Triple
T31661561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christchurch bus network |
E808015
|
entity |
| Predicate | mainInterchangeLocation |
P57330
|
FINISHED |
| Object | Christchurch city centre |
—
|
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: Christchurch city centre | Statement: [Christchurch bus network, mainInterchangeLocation, Christchurch city centre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainInterchangeLocation Context triple: [Christchurch bus network, mainInterchangeLocation, Christchurch city centre]
-
A.
interchangeLocation
chosen
Indicates a location where two or more routes, lines, or modes of transport connect, allowing passengers or goods to transfer between them.
-
B.
primaryExchangeLocation
Indicates the main place or venue where the exchange or transaction between the related entities primarily occurs.
-
C.
mainLocation
Indicates that one entity serves as the primary or central location associated with another entity.
-
D.
centralLocation
Indicates that one entity serves as the primary or central place associated with another entity.
-
E.
interchangeSystem
Indicates a relationship where two or more systems are connected in such a way that they can exchange or transfer items, data, or services between them.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 10:57 p.m.