Triple
T32827713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazil vs Croatia 2014 FIFA World Cup group match |
E839596
|
entity |
| Predicate | ownGoalTeam |
P104606
|
FINISHED |
| Object | Brazil national football team |
—
|
NE NERFINISHED |
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: Brazil national football team | Statement: [Brazil vs Croatia 2014 FIFA World Cup group match, ownGoalTeam, Brazil national football team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownGoalTeam Context triple: [Brazil vs Croatia 2014 FIFA World Cup group match, ownGoalTeam, Brazil national football team]
-
A.
ownGoalBeneficiaryTeam
chosen
Indicates the team that gains the scoring benefit when an own goal is committed against it.
-
B.
ownGoalBy
Indicates that a goal was accidentally scored against a team by the specified player (i.e., the player scored an own goal).
-
C.
goalScorerTeam
Indicates that a team is the one for which a particular goal scorer scored a goal.
-
D.
equalisingGoalTeam
Indicates that a team scores a goal which brings the score level with the opposing team.
-
E.
officialGoal
Indicates that something is the formally designated or institutionally recognized objective or target of an entity.
- 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_69f3493f22f88190ae6dd4bc15b6cf8d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:16 a.m.