Triple
T17663303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deportivo Mandiyú |
E440305
|
entity |
| Predicate | hasHistoricalSignificanceInFootball |
P72181
|
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: [Deportivo Mandiyú, hasHistoricalSignificanceInFootball, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalSignificanceInFootball Context triple: [Deportivo Mandiyú, hasHistoricalSignificanceInFootball, yes]
-
A.
hasHistoricalSignificance
Indicates that something possesses notable importance or influence within a historical context or period.
-
B.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
-
C.
roleInFootballHistory
chosen
Indicates the specific part or significance an entity has within the historical development, events, or legacy of football.
-
D.
notableFootballEvent
Indicates an event in football that is distinguished by particular significance, impact, or memorability within the sport.
-
E.
inSportHistory
Indicates that an entity is recorded or recognized as part of the historical events, records, or legacy of a particular sport.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea7f0ec81908eff43aa845584af |
completed | April 19, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 9:51 a.m.