Triple
T12013542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Euro 1996 |
E285964
|
entity |
| Predicate | qualifiedTeams |
P96366
|
FINISHED |
| Object | 16 |
—
|
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: 16 | Statement: [UEFA Euro 1996, qualifiedTeams, 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualifiedTeams Context triple: [UEFA Euro 1996, qualifiedTeams, 16]
-
A.
qualifiedTeam
Indicates that a team has met the necessary criteria or achieved the required results to advance or be accepted into a particular stage, event, or competition.
-
B.
eligibleTeamsFrom
Indicates that certain teams qualify or are allowed to originate from a specified source, context, or selection criteria.
-
C.
qualifiedTeamsCount
chosen
Indicates the number of teams that have successfully met the criteria to qualify for a given stage, event, or competition.
-
D.
coreTeams
Indicates that the entities are part of the same primary or central team within an organization or project.
-
E.
numberOfParticipatingTeamsInQualifying
Indicates the total number of teams that take part in the qualifying stage of a competition or event.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903d884488190b4450a98088208ef |
completed | April 10, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.