Triple
T33321854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PJ&B |
E853160
|
entity |
| Predicate | lineLengthCharacteristic |
P39661
|
FINISHED |
| Object | short shuttle branch line |
—
|
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: short shuttle branch line | Statement: [PJ&B, lineLengthCharacteristic, short shuttle branch line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineLengthCharacteristic Context triple: [PJ&B, lineLengthCharacteristic, short shuttle branch line]
-
A.
lineLengthType
Indicates the type or category used to characterize the length of a line.
-
B.
usesLineCharacteristic
Indicates that one entity employs or is based on a specific characteristic or property of a line.
-
C.
lengthStyle
Indicates how the extent or duration of something is expressed, formatted, or stylistically represented.
-
D.
hasLineLength
chosen
Indicates that one entity has, is characterized by, or is associated with a specific line length value.
-
E.
length
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:33 a.m.