Triple
T32319126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Europe/Brussels |
E825723
|
entity |
| Predicate | longitudeApproxOfReferenceCity |
P101838
|
FINISHED |
| Object | 4.35 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: 4.35 E | Statement: [Europe/Brussels, longitudeApproxOfReferenceCity, 4.35 E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longitudeApproxOfReferenceCity Context triple: [Europe/Brussels, longitudeApproxOfReferenceCity, 4.35 E]
-
A.
hostCityLongitude
Indicates the longitudinal coordinate of the city that serves as the host location for an event or entity.
-
B.
hostCityLatitude
Indicates the geographic latitude coordinate of the city that serves as the host location for an event or entity.
-
C.
typicalCityLongitude
chosen
Indicates the standard or representative longitude value associated with a given city.
-
D.
homeCityLatitude
Indicates the geographic latitude coordinate associated with an entity’s home city.
-
E.
locationRelativeToLargestCity
Indicates how a place is spatially positioned or oriented in relation to the largest city in a given area or region.
- 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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bdbe13748190854e7a42335bf6cd |
completed | May 3, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:46 a.m.