Triple
T5837820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian National Opera and Ballet |
E129515
|
entity |
| Predicate | coordinatesOfHomeVenue |
P1573
|
FINISHED |
| Object | 59.907°N 10.753°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: 59.907°N 10.753°E | Statement: [Norwegian National Opera and Ballet, coordinatesOfHomeVenue, 59.907°N 10.753°E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinatesOfHomeVenue Context triple: [Norwegian National Opera and Ballet, coordinatesOfHomeVenue, 59.907°N 10.753°E]
-
A.
coordinateLocation
chosen
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
B.
headquartersCoordinates
Indicates the geographic coordinates where an entity’s main headquarters is located.
-
C.
homeVenueCurrentName
Indicates the current official name of the venue that serves as an entity’s home location.
-
D.
coordinates of museum
Indicates that a museum is associated with specific geographic coordinates (such as latitude and longitude) representing its location.
-
E.
homeVenueCountry
Indicates the country in which an entity’s primary or home venue is located.
- 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03341e5888190a5f219b6f92cb161 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.