Triple
T6479180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R44 subway cars |
E146145
|
entity |
| Predicate | fleetNumbersNYCT |
P71145
|
FINISHED |
| Object | 100–399 |
—
|
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: 100–399 | Statement: [R44 subway cars, fleetNumbersNYCT, 100–399]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleetNumbersNYCT Context triple: [R44 subway cars, fleetNumbersNYCT, 100–399]
-
A.
bronxLine
Indicates a relationship where something is part of, associated with, or runs along the Bronx transit or route line.
-
B.
manhattanTrunkLine
Indicates a primary or central route, pathway, or connection running through a dense or core area, analogous to a main trunk line in Manhattan.
-
C.
notableManhattanStations
Indicates that there exists a notable or significant train or transit station located in Manhattan.
-
D.
subwayServices
Indicates that one entity provides or operates subway transportation services for another entity or area.
-
E.
brooklynTerminus
Indicates a relationship where a route, line, or service has its ending point or final stop located in Brooklyn.
- 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_69c008fec7408190af7b146dc63d9750 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c06a4e764c819086828bb841f588e0 |
completed | March 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69c0673f6d48819080e10c85155c7195 |
completed | March 22, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69c06822f73081908e6bb9edecbe77a6 |
completed | March 22, 2026, 10:07 p.m. |
Created at: March 22, 2026, 4:51 p.m.