Triple
T30171154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court Square station complex |
E766922
|
entity |
| Predicate | hasAdjacentStationOn7 |
P183728
|
FINISHED |
| Object | Hunters Point Avenue |
—
|
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: Hunters Point Avenue | Statement: [Court Square station complex, hasAdjacentStationOn7, Hunters Point Avenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentStationOn7 Context triple: [Court Square station complex, hasAdjacentStationOn7, Hunters Point Avenue]
-
A.
hasAdjacentStationOnU7
Indicates that one station is directly next to another station along the U7 line.
-
B.
hasAdjacentStationOnAC
Indicates that one station is directly next to another station along the AC line or route.
-
C.
hasAdjacentStationOnM
Indicates that one station is directly next to another station along metro line M, with no other stations in between.
-
D.
hasAdjacentStationOnE
Indicates that one station is directly adjacent to another station on the east side.
-
E.
hasAdjacentStationOnG
Indicates that one station is directly next to another station along line G in the network.
- 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_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: April 29, 2026, 7:24 p.m.