Triple
T35318888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chūō Shinkansen |
E1019981
|
entity |
| Predicate | plannedLineLengthPhase1 |
P22512
|
FINISHED |
| Object | approximately 286 km |
—
|
LITERAL FINISHED |
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: approximately 286 km | Statement: [Chūō Shinkansen, plannedLineLengthPhase1, approximately 286 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedLineLengthPhase1 Context triple: [Chūō Shinkansen, plannedLineLengthPhase1, approximately 286 km]
-
A.
plannedLength
Indicates the intended or scheduled duration or size of something as determined in advance, rather than its actual or realized extent.
-
B.
plannedTransmissionLineLength
Indicates the intended or projected length of a transmission line as specified in a plan or design.
-
C.
plannedExtensionLength
chosen
Indicates the intended or proposed length of an extension as specified in a plan or design.
-
D.
hasPlannedLine
Indicates that an entity is associated with a specific planned route or line intended for future or scheduled use.
-
E.
railwayLineLength
Indicates the total measured length of a railway line.
- F. None of above.
Provenance (3 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd0b92f42881908cd77e3f058adcc2 |
completed | May 7, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fd0a3d68d4819094d92040f7c48d7c |
completed | May 7, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:03 p.m.