Triple
T43242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AirTrain JFK |
E849
|
entity |
| Predicate | lineLength |
P266
|
FINISHED |
| Object | approximately 8.1 miles |
—
|
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 8.1 miles | Statement: [AirTrain JFK, lineLength, approximately 8.1 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineLength Context triple: [AirTrain JFK, lineLength, approximately 8.1 miles]
-
A.
length
chosen
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
B.
width
Indicates the measurement of how wide an entity is, typically the extent of its horizontal dimension from side to side.
-
C.
hasStandardLetterCount
Indicates that an entity’s associated text or label contains a number of letters that matches a predefined standard or expected count.
-
D.
leafMargin
Indicates the type or pattern of the edge or border of a leaf (e.g., smooth, serrated, lobed).
-
E.
numberOfStripes
Indicates the count of distinct stripe markings associated with an entity.
- 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_69a247a8f6c08190bac804906d62ed5a |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24c083ad081909c1122c8fb29efdc |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24aba9a2c81909f769a8f22e30c92 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:46 a.m.