Triple
T27765145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allen |
E701579
|
entity |
| Predicate | associatedWithTournamentEdition |
P51901
|
FINISHED |
| Object | 3rd FIFA World Cup |
—
|
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: 3rd FIFA World Cup | Statement: [Allen, associatedWithTournamentEdition, 3rd FIFA World Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithTournamentEdition Context triple: [Allen, associatedWithTournamentEdition, 3rd FIFA World Cup]
-
A.
linkedToTournamentCycle
Indicates that an entity is associated with, or participates in, a specific tournament cycle or series of tournament events.
-
B.
associatedWithCompetition
Indicates that there is a relationship or involvement between an entity and a specific competition or competitive event.
-
C.
associatedWithEdition
chosen
Indicates a relationship where something is linked or connected to a specific edition of a work or resource.
-
D.
followsTournament
Indicates that one entity regularly tracks, watches, or keeps up with the progress and events of a particular tournament.
-
E.
scoredInTournament
Indicates that an entity achieved a score or points during a particular tournament.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_6a006417d1f4819093b2da02dbf2ab22 |
completed | May 10, 2026, 10:55 a.m. |
| PD | Predicate disambiguation | batch_6a00634a7a748190ac4774493fce3d30 |
completed | May 10, 2026, 10:51 a.m. |
Created at: April 27, 2026, 4:30 p.m.