Triple
T32021640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North White Plains station |
E817704
|
entity |
| Predicate | yardFunction |
P173124
|
FINISHED |
| Object | storage and servicing of Metro-North trains |
—
|
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: storage and servicing of Metro-North trains | Statement: [North White Plains station, yardFunction, storage and servicing of Metro-North trains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yardFunction Context triple: [North White Plains station, yardFunction, storage and servicing of Metro-North trains]
-
A.
houseFunction
Indicates the functional role or primary use that a house serves (e.g., residential, commercial, mixed-use).
-
B.
gardenFeature
Indicates that one entity serves as a feature, element, or component within a garden associated with another entity.
-
C.
yardNumber
Indicates the identifying number assigned to a specific yard or yard-related unit within a larger system or location.
-
D.
gardenValue
Indicates that one entity assigns or possesses a particular value, worth, or importance in relation to a garden.
-
E.
gardenAccess
Indicates that one entity is permitted to enter or use a particular garden area.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b467759c8190905ba0ce0eceb5fb |
completed | May 3, 2026, 2:35 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: May 1, 2026, 12:16 a.m.