Triple
T24663607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibson neighborhood |
E610606
|
entity |
| Predicate | primarilyConnectedBy |
P86630
|
FINISHED |
| Object | Gibson railway station |
—
|
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: Gibson railway station | Statement: [Gibson neighborhood, primarilyConnectedBy, Gibson railway station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarilyConnectedBy Context triple: [Gibson neighborhood, primarilyConnectedBy, Gibson railway station]
-
A.
partlyConnectedBy
Indicates that two entities are linked or joined by something in an incomplete, partial, or not fully continuous way.
-
B.
formerlyConnectedTo
Indicates that two entities were once connected or associated in some way, but that connection no longer exists.
-
C.
primaryConnections
chosen
Indicates that there exists a main or most significant relationship or linkage between entities, distinguishing these connections from secondary or peripheral ones.
-
D.
notConnectedBy
Indicates that there is no direct link, path, or relationship connecting the referenced entities.
-
E.
connectedByStraitTo
Indicates that one entity is geographically linked to another by a narrow body of water known as a strait.
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 2:34 a.m.