Triple
T6356509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lexington Avenue Express (5) |
E143004
|
entity |
| Predicate | hasServiceMapSymbol |
P57606
|
FINISHED |
| Object | white 5 in a green circle |
—
|
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: white 5 in a green circle | Statement: [Lexington Avenue Express (5), hasServiceMapSymbol, white 5 in a green circle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceMapSymbol Context triple: [Lexington Avenue Express (5), hasServiceMapSymbol, white 5 in a green circle]
-
A.
hasServiceSymbolText
Indicates that a service symbol is associated with a specific textual representation.
-
B.
hasServiceSymbolShape
chosen
Indicates that an entity’s service symbol is represented using a particular geometric or visual shape.
-
C.
hasMapType
Indicates that one entity is associated with a specific type or category of map.
-
D.
hasServiceStructure
Indicates that one entity provides, contains, or is associated with a particular service-related structure or organizational framework for delivering a service.
-
E.
hasServiceClass
Indicates that an entity is associated with, or categorized under, a particular class or type of service.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067f37d0881909289bafb09e29298 |
completed | March 22, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69c060ec091c8190912aac44e1b8b1c9 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.