Triple
T2310956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1966 FIFA World Cup |
E51954
|
entity |
| Predicate | ballInstanceOf |
P3186
|
FINISHED |
| Object | association football |
—
|
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: association football | Statement: [1966 FIFA World Cup, ballInstanceOf, association football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballInstanceOf Context triple: [1966 FIFA World Cup, ballInstanceOf, association football]
-
A.
ballCondition
Indicates the specific state or status a ball is in, such as its physical condition, readiness for use, or compliance with required standards.
-
B.
ballType
chosen
Indicates the specific category or kind of ball associated with an entity.
-
C.
golfCourseInstanceOf
Indicates that a particular golf course is an instance of a specified golf course type or class.
-
D.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
E.
typeOfFootball
Indicates the specific code or variant of football that characterizes or classifies a given football-related 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.