Triple
T30171266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G |
E766926
|
entity |
| Predicate | entersManhattan |
P175362
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [G, entersManhattan, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entersManhattan Context triple: [G, entersManhattan, no]
-
A.
manhattanConnection
Indicates a direct or indirect connection or route between two entities specifically within the Manhattan area or grid.
-
B.
terminusInManhattan
Indicates that the endpoint or final stop of something (such as a route, line, or service) is located within Manhattan.
-
C.
lateNightManhattanTerminal
Indicates a terminal or endpoint that operates or is specifically used in Manhattan during late-night hours.
-
D.
onSideOfManhattan
Indicates that one entity is located on the same side of Manhattan as, or relative to, another reference entity.
-
E.
viaInBrooklyn
Indicates that something passes through, occurs in, or is routed by way of Brooklyn as part of its path or process.
- 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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6d1d916f881909575c2b22c416a5b |
completed | May 3, 2026, 4:40 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d0d331dc8190be5aa6bfc6365e67 |
completed | May 3, 2026, 4:36 a.m. |
Created at: April 29, 2026, 7:24 p.m.