Triple
T29710251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | France vs Australia |
E751758
|
entity |
| Predicate | usedGoalLineTechnology |
P156782
|
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: [France vs Australia, usedGoalLineTechnology, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedGoalLineTechnology Context triple: [France vs Australia, usedGoalLineTechnology, true]
-
A.
usesGoalLineTechnology
chosen
Indicates that an entity employs goal-line technology to determine whether a ball has fully crossed the goal line.
-
B.
isGoalLineStand
Indicates that an entity is positioned or formed as a defensive stand at the goal line, typically to prevent an opposing score.
-
C.
goldenGoalRuleUsed
Indicates that the outcome of a match or competition was determined using the golden goal rule, where the first score in extra time immediately ends the game.
-
D.
restartMethodWhenBallCrossesGoalLineOffDefender
Indicates that play is restarted using a specific method when the ball crosses the goal line after last being touched by a defending player.
-
E.
ownGoalDirectlyAllowed
Indicates that an own goal is permitted to be scored directly, without requiring any intervening touch or event.
- 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f672d8463481909f9144dbfa8be162 |
completed | May 2, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:30 p.m.