Triple
T14311151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nou Mestalla |
E354833
|
entity |
| Predicate | hasPlannedScoreboards |
P2583
|
FINISHED |
| Object | giant video screens |
—
|
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: giant video screens | Statement: [Nou Mestalla, hasPlannedScoreboards, giant video screens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedScoreboards Context triple: [Nou Mestalla, hasPlannedScoreboards, giant video screens]
-
A.
hasScoreboard
chosen
Indicates that one entity is equipped with or associated with a scoreboard used to display scores or results.
-
B.
usedOnScoreboards
Indicates that something is employed or displayed specifically on scoreboards.
-
C.
hasScoreboardLocation
Indicates the spatial or logical position where a scoreboard is placed or associated within a given context.
-
D.
hasScoreboardType
Indicates the specific kind or category of scoreboard associated with an entity.
-
E.
hasScoreSystem
Indicates that an entity uses, is governed by, or is associated with a particular scoring or rating system.
- 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_69d8278ed42c8190b9f882dcce611347 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de85b386d0819087d14f3ce84a1997 |
completed | April 14, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a8f81f08190af737e1654847aa6 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:12 a.m.