Triple
T5688975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Men's Olympic Football Tournament |
E125381
|
entity |
| Predicate | overagePlayersRuleIntroduced |
P23145
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Men's Olympic Football Tournament, overagePlayersRuleIntroduced, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overagePlayersRuleIntroduced Context triple: [Men's Olympic Football Tournament, overagePlayersRuleIntroduced, 1996]
-
A.
allowsOveragePlayers
chosen
Indicates that a context, rule, or system permits participation or inclusion of players who exceed a specified age limit.
-
B.
hasDesignatedPlayerRule
Indicates that a sports league or competition uses a designated player rule allowing certain players to be treated differently for roster or salary purposes.
-
C.
introducedOvertimeShootout
Indicates that an overtime shootout format was implemented or brought into use at a particular point in time.
-
D.
formerOvertimeRule
Indicates that a previously applicable overtime rule or regulation no longer applies in the current context.
-
E.
jerseyNumberRules
Indicates rules or constraints governing which jersey numbers may be assigned or used.
- 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c0e0408190ab6c3cd3f907e80f |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.