Triple
T25554789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Collins Street, Melbourne |
E640539
|
entity |
| Predicate | easternEndNickname |
P69635
|
FINISHED |
| Object | Paris End |
—
|
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: Paris End | Statement: [Collins Street, Melbourne, easternEndNickname, Paris End]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: easternEndNickname Context triple: [Collins Street, Melbourne, easternEndNickname, Paris End]
-
A.
easternTerminusTown
Indicates that a given town serves as the eastern endpoint or terminus of a route, line, or corridor.
-
B.
regionalNickname
chosen
Indicates that one entity is an informal or colloquial name used for another entity within a specific geographic region.
-
C.
easternTerminusLocatedOn
Indicates that the eastern endpoint of a route, line, or path is situated on or at a specified feature or location.
-
D.
easternBaseOf
Indicates that one entity is located at or forms the eastern base or foot of another entity.
-
E.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
- 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8c8e1688190af8d9be4660c4888 |
completed | May 2, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 3:38 p.m.