Triple
T12829773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goal of the Century |
E306752
|
entity |
| Predicate | matchResultForScorerTeam |
P56461
|
FINISHED |
| Object | win |
—
|
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: win | Statement: [Goal of the Century, matchResultForScorerTeam, win]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchResultForScorerTeam Context triple: [Goal of the Century, matchResultForScorerTeam, win]
-
A.
goalScorerTeam
Indicates that a team is the one for which a particular goal scorer scored a goal.
-
B.
resultOfMatch
chosen
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
-
C.
coachOfScoringTeam
Indicates that one entity is the coach of the team that scored in a particular play or event.
-
D.
decidingScoreTeam
Indicates the team whose score ultimately determines the outcome or winner in a game or match.
-
E.
scoredInMatch
Indicates that an entity (typically a player or team) scored during a particular 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa08cd481909a946046ba63809f |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:34 p.m.