Triple
T3468629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelaide United FC |
E73197
|
entity |
| Predicate | locationCoordinatesApprox |
P10760
|
FINISHED |
| Object | -34.9, 138.57 (Coopers Stadium) |
—
|
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: -34.9, 138.57 (Coopers Stadium) | Statement: [Adelaide United FC, locationCoordinatesApprox, -34.9, 138.57 (Coopers Stadium)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationCoordinatesApprox Context triple: [Adelaide United FC, locationCoordinatesApprox, -34.9, 138.57 (Coopers Stadium)]
-
A.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
B.
locationSignedNear
Indicates that an entity’s location is in close physical proximity to another specified place or reference point.
-
C.
hasApproximateCoordinates
chosen
Indicates that an entity is associated with location coordinates that are estimated or imprecise rather than exact.
-
D.
mapLocation
Indicates a relationship where an entity is associated with a specific position or area on a map.
-
E.
hasApproximateLocation
Indicates that an entity is associated with a location that is known only imprecisely or within a general area rather than an exact position.
- 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_69ad85b2fed48190948c8765e453d270 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbb376d288190abac85f2ffa853dc |
completed | March 8, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:17 p.m.