Triple
T1263095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English Football League |
E12541
|
entity |
| Predicate | tierCoverage |
P21531
|
FINISHED |
| Object | second to fourth tiers of English football |
—
|
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: second to fourth tiers of English football | Statement: [English Football League, tierCoverage, second to fourth tiers of English football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierCoverage Context triple: [English Football League, tierCoverage, second to fourth tiers of English football]
-
A.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
-
B.
mayCoverArea
chosen
Indicates that one entity is permitted or able to extend over, include, or encompass a specified spatial area.
-
C.
regionCoverage
Indicates that one entity geographically spans, includes, or serves the area defined by another entity.
-
D.
fieldCovered
Indicates that a specified field or area is physically or functionally covered by some material, object, or condition.
-
E.
reignCoverage
Indicates the temporal span or extent over which a ruler’s reign or authority is in effect.
- 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfc8d6908190a5b2cf1051cc6d5e |
completed | March 1, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69a4bb7058e88190825b0cba5ee60b51 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:50 p.m.