Triple
T23598035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Cup 1997–98 with Inter Milan |
E582671
|
entity |
| Predicate | roundReached |
P92022
|
FINISHED |
| Object | final |
—
|
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: final | Statement: [UEFA Cup 1997–98 with Inter Milan, roundReached, final]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roundReached Context triple: [UEFA Cup 1997–98 with Inter Milan, roundReached, final]
-
A.
reachedRound
chosen
Indicates that an entity has advanced to or attained a particular round or stage within a process, event, or competition.
-
B.
roundCount
Indicates the number of discrete rounds or iterations that have occurred or are allocated within a process, event, or interaction.
-
C.
hasRound
Indicates that an entity possesses, includes, or is associated with a particular round (e.g., a round of an event, game, or process).
-
D.
hasRoudNumber
Indicates that an entity is associated with or assigned a specific round number within a sequence of rounds or stages.
-
E.
stageReached
Indicates that a process, task, or entity has arrived at or completed a specific stage or phase within a defined progression.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b091992c819085f8aa6cb91cb76a |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:43 p.m.