Triple
T563958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australia/Melbourne |
E13512
|
entity |
| Predicate | longitudeApproxPrincipalCity |
P1282
|
FINISHED |
| Object | 144.9631 |
—
|
LITERAL FINISHED |
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: 144.9631 | Statement: [Australia/Melbourne, longitudeApproxPrincipalCity, 144.9631]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longitudeApproxPrincipalCity Context triple: [Australia/Melbourne, longitudeApproxPrincipalCity, 144.9631]
-
A.
coordinateLongitude
chosen
Indicates the east–west geographic position of an entity on the Earth’s surface, expressed as a longitude value.
-
B.
coordinateLatitude
Indicates the north–south geographic position of an entity on the Earth’s surface, expressed as a latitude coordinate.
-
C.
nearestMajorCity
Indicates that one city is the closest significant urban center to another location or city compared to all other major cities.
-
D.
primaryCity
Indicates that one city serves as the main or most important city associated with a given region, entity, or context.
-
E.
distanceFromCapital
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49a735b2881908293ad21ad41cdd6 |
completed | March 1, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69a494c044648190a98589ab18935216 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.