Triple
T3854182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourth Division 1991–92 play-offs |
E85370
|
entity |
| Predicate | semiFinalFormat |
P52356
|
FINISHED |
| Object | two-legged home-and-away ties |
—
|
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: two-legged home-and-away ties | Statement: [Fourth Division 1991–92 play-offs, semiFinalFormat, two-legged home-and-away ties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: semiFinalFormat Context triple: [Fourth Division 1991–92 play-offs, semiFinalFormat, two-legged home-and-away ties]
-
A.
semifinalResult
Indicates the outcome or score of a semifinal-stage contest or match between competitors.
-
B.
semifinalist
Indicates that an entity has advanced to the semifinal round or stage of a competition, selection process, or tournament.
-
C.
semiFinalsHeld
Indicates that the semi-final stage of a competition or tournament has taken place or is being conducted.
-
D.
semifinalMatchup
Indicates that two competitors or teams are paired to compete against each other in a semifinal round of a tournament or competition.
-
E.
semifinalDate
Indicates the scheduled calendar date on which a semifinal round of a competition or tournament takes place.
- 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_69aed936de1c81908f91bed80f70abb2 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec0438308190865ff74bee5a1cf2 |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee752c8a48190a670f73ed0bf1e61 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aeeb828fb08190901d51edbe8bd304 |
completed | March 9, 2026, 3:47 p.m. |
Created at: March 9, 2026, 3:19 p.m.