Triple
T12490612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Cup 2008–09 with Chelsea |
E298550
|
entity |
| Predicate | roundEntered |
P72751
|
FINISHED |
| Object | Third Round Proper |
—
|
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: Third Round Proper | Statement: [FA Cup 2008–09 with Chelsea, roundEntered, Third Round Proper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roundEntered Context triple: [FA Cup 2008–09 with Chelsea, roundEntered, Third Round Proper]
-
A.
round
Indicates that an entity has a circular or approximately circular shape or form.
-
B.
roundOf
chosen
Indicates that one event, match, or game occurs as a specific stage or phase within a larger competition or tournament.
-
C.
roundCount
Indicates the number of discrete rounds or iterations that have occurred or are allocated within a process, event, or interaction.
-
D.
rounded
Indicates that one entity has been made or become rounder or more curved in shape, often by smoothing or adjusting its edges or values.
-
E.
reachedRound
Indicates that an entity has advanced to or attained a particular round or stage within a process, event, or competition.
- 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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e8a706c8190873623eab7db607d |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d41f3cc8190a3331fb9a895306f |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.