Triple
T30367138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1970 FIBA World Championship |
E772449
|
entity |
| Predicate | hasFinalRound |
P195970
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [1970 FIBA World Championship, hasFinalRound, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinalRound Context triple: [1970 FIBA World Championship, hasFinalRound, yes]
-
A.
hasFinalTournament
Indicates that an entity is associated with a specific tournament that serves as its final or concluding competition.
-
B.
isFinalsOf
Indicates that one entity represents the final or concluding stage, round, or version of another entity.
-
C.
hasNumberOfFinalists
Indicates the relationship between an entity and the count of finalists associated with it.
-
D.
hasFinalsSeries
Indicates that there exists a specific finals series associated with or assigned to a given entity.
-
E.
hasFinale
Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) of another entity.
- F. None of above. chosen
Provenance (4 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdfbafe32081909c62653ff4fc155c |
completed | May 8, 2026, 3:05 p.m. |
| PD | Predicate disambiguation | batch_69fdf64db4a881908f8250e24ae3cefb |
completed | May 8, 2026, 2:42 p.m. |
| PDg | Predicate description generation | batch_69fdfbae00e481908a2e4558b9dee07e |
completed | May 8, 2026, 3:05 p.m. |
Created at: April 29, 2026, 7:58 p.m.