Triple
T6729265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estádio José Alvalade |
E153592
|
entity |
| Predicate | hasSpectatorSport |
P27495
|
FINISHED |
| Object | association football |
—
|
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: association football | Statement: [Estádio José Alvalade, hasSpectatorSport, association football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpectatorSport Context triple: [Estádio José Alvalade, hasSpectatorSport, association football]
-
A.
spectatorSport
chosen
Indicates that an activity is primarily performed for the enjoyment of an audience watching rather than for direct participation.
-
B.
hasSportingEvent
Indicates that a sporting event is associated with, held at, or organized by a given entity.
-
C.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
D.
hasMajorSport
Indicates that an entity is associated with or participates in a primary or most prominent sport.
-
E.
hasSportingContext
Indicates that something is associated with, occurs within, or is relevant to a particular sporting or athletic context.
- 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_69c6880bdd68819097de8b6099992682 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d354177481908ab3cf5437c095e2 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d08e8a2c8190ae4e8d8c039be7ce |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:08 p.m.