Triple
T16575978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuuk Stadium |
E402709
|
entity |
| Predicate | servesAsMainVenueFor |
P39293
|
FINISHED |
| Object | local football competitions |
—
|
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: local football competitions | Statement: [Nuuk Stadium, servesAsMainVenueFor, local football competitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAsMainVenueFor Context triple: [Nuuk Stadium, servesAsMainVenueFor, local football competitions]
-
A.
holdsTournamentsIn
Indicates that an entity organizes or conducts tournaments at or within a specified location.
-
B.
hasMajorVenue
Indicates that an entity is associated with a primary or principal venue where its main activities or events take place.
-
C.
sportsVenueFor
chosen
Indicates that a venue is used as the location or facility where a particular sport or sporting event takes place.
-
D.
significantVenueFor
Indicates that a venue plays an important or notable role in relation to a particular entity, event, or activity.
-
E.
sportsVenueLocatedIn
Indicates that a sports venue is geographically situated within a specified location or administrative area.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3595cb65481909be62a52deff3d44 |
completed | April 18, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.