Triple
T27702071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federale 102 |
E698452
|
entity |
| Predicate | followedInTournamentSequence |
P179475
|
FINISHED |
| Object | match ball of the 1938 FIFA World Cup |
—
|
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: match ball of the 1938 FIFA World Cup | Statement: [Federale 102, followedInTournamentSequence, match ball of the 1938 FIFA World Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedInTournamentSequence Context triple: [Federale 102, followedInTournamentSequence, match ball of the 1938 FIFA World Cup]
-
A.
precededInTournamentSequence
Indicates that one participant or event occurred earlier than another in the ordered sequence of a tournament.
-
B.
followedByTournament
Indicates that one event or period is immediately succeeded by a tournament.
-
C.
followsTournament
Indicates that one entity regularly tracks, watches, or keeps up with the progress and events of a particular tournament.
-
D.
scoredInTournament
Indicates that an entity achieved a score or points during a particular tournament.
-
E.
playedInTournament
Indicates that an entity participated as a competitor or player in a specific tournament.
- 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_69ef590ea74081908f0cd7500d85fa27 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 27, 2026, 2:57 p.m.