Triple
T22605028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Fahd Cup |
E566531
|
entity |
| Predicate | lastEditionAsKingFahdCup |
P10601
|
FINISHED |
| Object | 1995 |
—
|
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: 1995 | Statement: [King Fahd Cup, lastEditionAsKingFahdCup, 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastEditionAsKingFahdCup Context triple: [King Fahd Cup, lastEditionAsKingFahdCup, 1995]
-
A.
lastEffectiveShah
Indicates that the subject is the final individual to have effectively held the position or role of Shah (monarch) in a given context.
-
B.
finalPlayedIn
Indicates that an entity participated in the final match or round of a competition or tournament in a specified context.
-
C.
lastNominalShah
Indicates that the subject is the final individual to hold the title or position of Shah in a nominal (in-name-only or largely symbolic) capacity.
-
D.
lastEdition
chosen
Indicates that one entity is the most recent or final edition/version within a series or sequence of editions.
-
E.
lastWinner
Indicates that one entity is the most recent winner in a sequence of competitions, contests, or events involving the other 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_69e245884860819081046ce07d5872c4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f162709d808190af83837104a190f9 |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:53 p.m.