Triple
T22721603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5 (New York City Subway service) |
E561874
|
entity |
| Predicate | identificationLetterOrNumber |
P70157
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [5 (New York City Subway service), identificationLetterOrNumber, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identificationLetterOrNumber Context triple: [5 (New York City Subway service), identificationLetterOrNumber, 5]
-
A.
letterOrNumberDesignation
chosen
Indicates that something is identified or labeled using a specific letter, number, or combination of both.
-
B.
identificationNumberFormat
Indicates the specific structural pattern or rules that an identification number must follow.
-
C.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
D.
identificationType
Indicates the specific kind or category of identification associated with an entity or relationship.
-
E.
inscriptionNumber
Indicates the identifying number assigned to a specific inscription within a collection or system.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17911a4fc81908a125209aea77e22 |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:19 p.m.