Triple
T17799450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argentina at 1994 FIFA World Cup |
E444380
|
entity |
| Predicate | totalMatchesPlayed |
P128970
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [Argentina at 1994 FIFA World Cup, totalMatchesPlayed, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalMatchesPlayed Context triple: [Argentina at 1994 FIFA World Cup, totalMatchesPlayed, 4]
-
A.
matchesPlayedIn
Indicates that a particular match was played in a specified location, event, or competition context.
-
B.
leagueMatchesPlayed
Indicates the number of matches an entity has participated in within a specific league competition.
-
C.
qualificationMatchesPlayed
Indicates that the number of qualification matches associated with an entity has been played or completed.
-
D.
numberOfTestMatches
Indicates the total count of test matches associated with a given entity (such as a player, team, or series) in the relationship.
-
E.
odiMatchesPlayed
Indicates the number of One Day International (ODI) cricket matches that have been played by or between the referenced entities.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487fe19dc8190b7e9dc96f39e0861 |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3db7704588190a34a422421152173 |
completed | April 18, 2026, 7:28 p.m. |
Created at: April 10, 2026, 10:13 a.m.