Triple
T29708903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1922 South American Championship |
E751720
|
entity |
| Predicate | hadPlayoffMatch |
P167623
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [1922 South American Championship, hadPlayoffMatch, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPlayoffMatch Context triple: [1922 South American Championship, hadPlayoffMatch, true]
-
A.
hasPlayoffsWith
Indicates that two entities participate together in the same playoff series, bracket, or postseason competition.
-
B.
hasPlayoffRoundBefore
Indicates that one playoff round occurs earlier in the sequence than another playoff round within the same competition or season.
-
C.
wonPlayoffs
Indicates that a team or player emerged as the overall victor in a playoff series or postseason competition.
-
D.
playoffRoundReached
Indicates the specific stage or round of a playoff series that an entity has advanced to or reached.
-
E.
hasPositionInPlayoffs
Indicates that an entity holds a specific rank or standing within a playoff competition or bracket.
- F. None of above. chosen
Provenance (4 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672d7511c8190b10daa0435111785 |
completed | May 2, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 7:29 p.m.