Triple
T27760625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argyle |
E701458
|
entity |
| Predicate | DevonDerbyOpponent |
P45389
|
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: [Argyle, DevonDerbyOpponent, Exeter City F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DevonDerbyOpponent Context triple: [Argyle, DevonDerbyOpponent, Exeter City F.C.]
-
A.
cityDerbyHosted
Indicates that a particular city served as the host location for a specified derby event.
-
B.
cityDerbyName
Indicates that a city is known by a particular derby (rivalry match) name.
-
C.
playsInDerbyWith
chosen
Indicates that two entities participate together as opponents or competitors in the same derby event or match.
-
D.
leagueCupFinalOpponent
Indicates that one entity is the opponent faced by another entity in the final match of a league cup competition.
-
E.
ShrovetideFootballTeams
Indicates that the related entities are opposing teams participating in a Shrovetide football match.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63765603c8190a782bd8139a5a862 |
completed | May 2, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:26 p.m.