Triple
T22651825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stade Auguste-Delaune |
E559111
|
entity |
| Predicate | hasLocationCoordinates |
P10142
|
FINISHED |
| Object | 49.249°N 4.024°E |
—
|
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: 49.249°N 4.024°E | Statement: [Stade Auguste-Delaune, hasLocationCoordinates, 49.249°N 4.024°E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocationCoordinates Context triple: [Stade Auguste-Delaune, hasLocationCoordinates, 49.249°N 4.024°E]
-
A.
hasCoordinates
chosen
Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
-
B.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
C.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
D.
hasCoordinatesType
Indicates that an entity is associated with a specific type or system of coordinates used to define its position.
-
E.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703c5538819089d9b5349f26ea6d |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:06 p.m.