Triple
T19846763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stade Maurice-Trélut |
E476880
|
entity |
| Predicate | hasSpectatorZones |
P13691
|
FINISHED |
| Object | covered stands |
—
|
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: covered stands | Statement: [Stade Maurice-Trélut, hasSpectatorZones, covered stands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpectatorZones Context triple: [Stade Maurice-Trélut, hasSpectatorZones, covered stands]
-
A.
hasSpectatorArea
chosen
Indicates that a location or facility includes a designated area intended for spectators to observe an event or activity.
-
B.
hasSpectatorType
Indicates that an event or activity is associated with a particular category or type of spectator.
-
C.
hasSpectators
Indicates that an event, activity, or occurrence is being watched or attended by one or more spectators.
-
D.
hasSpectatorAmenities
Indicates that a place or facility provides amenities or features intended for the comfort or convenience of spectators.
-
E.
spectatorAreaType
Indicates the specific kind or category of area designated for spectators in a venue or event setting.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65809da2c8190bb579ef42513b74d |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.