Triple
T24676563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ciudadela de Pamplona |
E611000
|
entity |
| Predicate | hasSportsAreas |
P114870
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Ciudadela de Pamplona, hasSportsAreas, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSportsAreas Context triple: [Ciudadela de Pamplona, hasSportsAreas, yes]
-
A.
hasSportsGround
Indicates that an entity possesses, includes, or is associated with a sports ground or athletic field as part of its facilities or area.
-
B.
hasSportsPrecinct
chosen
Indicates that an entity includes, contains, or is associated with a designated area or complex specifically intended for sports activities or facilities.
-
C.
hasSportsService
Indicates that an entity provides or is associated with a sports-related service.
-
D.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
E.
hasSportsFunction
Indicates that an entity serves a role, purpose, or function related to sports activities or sports-related operations.
- 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_69e2c4d5c2dc8190ac857dea25ec6ce9 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:05 a.m.