Triple
T8920047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Didcot Town F.C. |
E212390
|
entity |
| Predicate | competitiveScope |
P15208
|
FINISHED |
| Object | regional |
—
|
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: regional | Statement: [Didcot Town F.C., competitiveScope, regional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitiveScope Context triple: [Didcot Town F.C., competitiveScope, regional]
-
A.
competitiveContext
Indicates a situation in which entities are engaged in or influenced by competition with one another.
-
B.
promotionScope
Indicates the range or extent within which a promotion or promotional offer is valid or applicable.
-
C.
hasCompetitionScope
chosen
Indicates the extent or boundaries within which a competition, contest, or competitive activity is defined or applies.
-
D.
competitiveDiscipline
Indicates a relationship where an entity participates in or is associated with a structured, rule-based activity or field in which individuals or groups compete against each other.
-
E.
competitiveEffect
Indicates that one entity’s actions or presence influence another entity’s ability to compete, typically by enhancing or diminishing its competitive position or performance.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc664f099c8190be6d20a4574212ca |
completed | April 1, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.