Triple
T30209081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farnborough F.C. |
E768019
|
entity |
| Predicate | localDerbyWith |
P52081
|
FINISHED |
| Object | Aldershot Town 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: Aldershot Town F.C. | Statement: [Farnborough F.C., localDerbyWith, Aldershot Town F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localDerbyWith Context triple: [Farnborough F.C., localDerbyWith, Aldershot Town F.C.]
-
A.
regionDerby
chosen
Indicates a competitive match or rivalry that takes place between teams or participants from the same geographic region.
-
B.
isFromCityWithDerby
Indicates that an entity originates from a city that has a football (or sports) derby with another team from the same city.
-
C.
isDerby
Indicates that a competition or match is a derby, typically involving teams or participants from the same locality or with a strong rivalry.
-
D.
relatedDerby
Indicates that two entities are connected through participation in, association with, or relevance to the same derby event or competition.
-
E.
hasHomeDerbyFor
Indicates that one entity serves as the home venue or location where another entity’s derby event is held.
- 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_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 7:32 p.m.