Triple
T20985126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City Council districts |
E516872
|
entity |
| Predicate | cannotCross |
P119401
|
FINISHED |
| Object | city boundary |
—
|
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: city boundary | Statement: [New York City Council districts, cannotCross, city boundary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotCross Context triple: [New York City Council districts, cannotCross, city boundary]
-
A.
cannotBeCrossedBy
chosen
Indicates that one entity forms a barrier or obstacle that another entity is unable to pass through or traverse.
-
B.
notCrossing
Indicates that two entities do not intersect, overlap, or pass through each other in space or along their paths.
-
C.
mayCross
Indicates that one entity is permitted or allowed to cross or pass over another entity or boundary.
-
D.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
E.
crossedBy
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe218748190a987b9f922d9be1b |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:48 p.m.