Triple
T34771613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L0 Series maglev trainsets |
E1002376
|
entity |
| Predicate | testingLine |
P181598
|
FINISHED |
| Object | Yamanashi Maglev Test Line |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Yamanashi Maglev Test Line | Statement: [L0 Series maglev trainsets, testingLine, Yamanashi Maglev Test Line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testingLine Context triple: [L0 Series maglev trainsets, testingLine, Yamanashi Maglev Test Line]
-
A.
lineUse
Indicates how a particular line (such as a route, track, or service line) is utilized or purposed within a system or network.
-
B.
definedLine
Indicates that a specific line (such as a boundary, path, or reference line) has been formally established or specified within a given context.
-
C.
supportsLine
Indicates that one entity provides structural, functional, or conceptual backing or reinforcement to a particular line (such as a line of text, code, argument, or physical alignment).
-
D.
formedLine
Indicates that an entity has arranged itself or others into a line or linear formation.
-
E.
линия
Indicates a relationship where something is a line or forms a linear connection or boundary between points or areas.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f77ff804f08190b431a31e6179ace4 |
completed | May 3, 2026, 5:03 p.m. |
Created at: May 3, 2026, 3:59 p.m.