Triple
T1970556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leicester City F.C. |
E42788
|
entity |
| Predicate | reachedStage |
P9657
|
FINISHED |
| Object | 2016–17 UEFA Champions League quarter-finals |
—
|
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: 2016–17 UEFA Champions League quarter-finals | Statement: [Leicester City F.C., reachedStage, 2016–17 UEFA Champions League quarter-finals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reachedStage Context triple: [Leicester City F.C., reachedStage, 2016–17 UEFA Champions League quarter-finals]
-
A.
stageOf
chosen
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
B.
stages
Indicates that one entity organizes, presents, or sets up another entity (such as an event, performance, or situation) to take place or be displayed.
-
C.
stageName
Indicates that one entity is the performance or professional name used by another entity.
-
D.
secondReachedBy
Indicates that a particular point, state, or entity is reached as the second in order by another entity or process.
-
E.
stoppedAt
Indicates that an entity has come to a halt or pause at a specific location or point in time.
- 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_69a88711151c8190940b2572095059d7 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3d2836c8190a35cb6d8e2dd4bdf |
completed | March 7, 2026, 5:12 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.