Triple
T28021040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crosstown Local |
E707687
|
entity |
| Predicate | operatesEntirelyWithin |
P50003
|
FINISHED |
| Object | Brooklyn |
—
|
NE NERFINISHED |
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: Brooklyn | Statement: [Crosstown Local, operatesEntirelyWithin, Brooklyn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesEntirelyWithin Context triple: [Crosstown Local, operatesEntirelyWithin, Brooklyn]
-
A.
runsEntirelyWithin
chosen
Indicates that one entity’s spatial or temporal extent is completely contained within the boundaries of another entity, without crossing or exceeding them.
-
B.
operatesWithin
Indicates that one entity carries out its activities, functions, or operations inside the scope, boundaries, or jurisdiction defined by another entity.
-
C.
operatesOutsideOf
Indicates that an entity performs its activities or functions beyond the boundaries or jurisdiction of a specified entity or context.
-
D.
operatesPrimarilyOn
Indicates that one entity is mainly or chiefly used to act upon, affect, or process another entity.
-
E.
isOperatedIn
Indicates that an entity carries out its operations or activities within a specified location, region, or jurisdiction.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: April 27, 2026, 8:10 p.m.