Triple
T36454496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T train (planned) |
E898112
|
entity |
| Predicate | plannedToServe |
P33500
|
FINISHED |
| Object | Upper East Side |
—
|
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: Upper East Side | Statement: [T train (planned), plannedToServe, Upper East Side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedToServe Context triple: [T train (planned), plannedToServe, Upper East Side]
-
A.
intendedToServe
chosen
Indicates that one entity was designed, planned, or purposed specifically to benefit, assist, or fulfill the needs of another entity.
-
B.
laterServedIn
Indicates that one entity subsequently held a service position or role in which another entity had previously served.
-
C.
sendsToServe
Indicates that one entity dispatches another entity to perform duties or fulfill a role at a specified place or for a particular purpose.
-
D.
servedDuring
Indicates that one entity held a role, position, or performed a function within the time period defined by another entity.
-
E.
isServed
Indicates that one entity provides or delivers a service, product, or assistance to another 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 3, 2026, 4:10 p.m.