Triple
T10742548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribuna |
E253362
|
entity |
| Predicate | belongsToSport |
P17094
|
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: [Tribuna, belongsToSport, association football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToSport Context triple: [Tribuna, belongsToSport, association football]
-
A.
associatedWithTeamSport
chosen
Indicates a relationship where an entity is connected to, involved in, or participates in a team-based sport.
-
B.
memberOfSportsLeague
Indicates that an entity is formally part of, or participates as a member in, a specific sports league.
-
C.
memberOfSportsTeamOwned
Indicates that an entity is a member of a sports team that is owned by another specified entity.
-
D.
isInSportSystemOf
Indicates that one entity belongs to, is organized within, or operates under the structure of a particular sport system or sports organizational framework of another entity.
-
E.
hasRelativeInSport
Indicates that one entity has a family member who participates or is involved in a sport-related activity or profession.
- 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_69d6aa5e51e8819095f06881cecf152e |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d710456ec88190ad8aff8804d13aa9 |
completed | April 9, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69d6f30df9948190ab3cdc33977fac14 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:15 p.m.