Triple
T2000189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Cup 1967–68 |
E43450
|
entity |
| Predicate | finalAfterExtraTime |
P35409
|
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: [European Cup 1967–68, finalAfterExtraTime, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalAfterExtraTime Context triple: [European Cup 1967–68, finalAfterExtraTime, true]
-
A.
decidedInRegulationTime
Indicates that the outcome of a contest or match was determined within the standard allotted duration, without requiring any extra time or tiebreak procedures.
-
B.
finalLeague
Indicates the league or competition in which an entity ultimately ends up or is officially classified, typically after all stages or transitions are complete.
-
C.
finalMatchType
Indicates the specific category or format of the concluding or decisive match in a series or competition.
-
D.
finalScore
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
E.
usesExtraTimeInLaterRounds
Indicates that an entity allocates or consumes additional time during later stages or rounds of an activity, process, or event.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb91055d88190a980e7b42e5895d4 |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb79c97d48190b3147430ed39faa9 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb90ec7948190bbfb0329e9e67cca |
completed | March 7, 2026, 5:35 a.m. |
Created at: March 4, 2026, 7:37 p.m.