Triple
T22719273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City bus routes in Manhattan |
E561815
|
entity |
| Predicate | includesRoutePrefix |
P66954
|
FINISHED |
| Object | M |
—
|
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: M | Statement: [New York City bus routes in Manhattan, includesRoutePrefix, M]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesRoutePrefix Context triple: [New York City bus routes in Manhattan, includesRoutePrefix, M]
-
A.
includesRouteType
Indicates that one entity’s set of routes contains or covers a specific type or category of route associated with another entity.
-
B.
hasPrefix
chosen
Indicates that one entity occurs at the beginning of another entity, serving as its starting segment or initial substring.
-
C.
includesRouteBetween
Indicates that one entity (such as a service, plan, or network) contains or provides a specific route connecting two locations or points.
-
D.
isRouteFor
Indicates that one entity serves as a path, course, or channel used for traveling, transporting, or connecting to another entity.
-
E.
hasSuffixedRoute
Indicates that a route is a variant or extension of another base route, distinguished by an added suffix in its identifier.
- 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_69f1790fbf9c819082ba7b48801a7b39 |
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.