Triple
T21471449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Cup 1973–74 |
E529741
|
entity |
| Predicate | finalScoreFirstMatch |
P61386
|
FINISHED |
| Object | 1–1 after extra time |
—
|
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: 1–1 after extra time | Statement: [European Cup 1973–74, finalScoreFirstMatch, 1–1 after extra time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalScoreFirstMatch Context triple: [European Cup 1973–74, finalScoreFirstMatch, 1–1 after extra time]
-
A.
finalFirstMatchResult
Indicates that the referenced result is the first outcome in a sequence that is considered final or decisive for a given matching process.
-
B.
finalOfficialMatchScore
Indicates the conclusive, authoritative score assigned to a match after all reviews, adjustments, or validations are completed.
-
C.
finalGameScoreGame1
chosen
Indicates the final score recorded for the first game in a series or set of games.
-
D.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
-
E.
firstInternationalMatchResult
Indicates the outcome (such as win, loss, or draw) of an entity’s first international match.
- 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea13adfc819093324ae6fe66c3fd |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:18 p.m.