Triple
T30208999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2007–08 Conference Premier |
E768016
|
entity |
| Predicate | playOffWinner |
P144208
|
FINISHED |
| Object | Exeter City F.C. |
—
|
NE NERFINISHED |
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: Exeter City F.C. | Statement: [2007–08 Conference Premier, playOffWinner, Exeter City F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playOffWinner Context triple: [2007–08 Conference Premier, playOffWinner, Exeter City F.C.]
-
A.
playoffResult
Indicates the outcome of a playoff contest or series between competitors, such as who advanced or was eliminated.
-
B.
playoffChampions
chosen
Indicates that the subject entity has won the playoff competition and is recognized as the overall champion for that playoff series or season.
-
C.
playoffTrophyContested
Indicates that a particular playoff trophy is the object of competition in a given playoff series or tournament.
-
D.
playoffName
Indicates the designated name or title assigned to a specific playoff series, round, or event within a competition.
-
E.
semifinalWinner
Indicates that the subject entity has won a semifinal match or round, thereby advancing toward the final stage of a 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67fefbf6481909b37c1f7f4903985 |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:32 p.m.