Triple
T22961832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East of Scotland Football League |
E570919
|
entity |
| Predicate | integratedIntoPyramid |
P68306
|
FINISHED |
| Object | 2013–14 |
—
|
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: 2013–14 | Statement: [East of Scotland Football League, integratedIntoPyramid, 2013–14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratedIntoPyramid Context triple: [East of Scotland Football League, integratedIntoPyramid, 2013–14]
-
A.
integrationIntoPyramid
chosen
Indicates that one entity is incorporated as a component or level within a hierarchical pyramid structure defined by another entity.
-
B.
hasPyramid
Indicates that one entity possesses, contains, or features a pyramid in relation to another entity.
-
C.
hasPyramidStructure
Indicates that something possesses or exhibits a pyramid-like hierarchical or geometric structure.
-
D.
pyramidFunction
Indicates a functional or hierarchical relationship where one entity operates at the apex or controlling level over multiple subordinate entities, analogous to a pyramid structure.
-
E.
levelOnPyramid
Indicates the relative vertical tier or layer that an entity occupies within a pyramid structure.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f594fc8190816418486b798198 |
completed | April 29, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:47 p.m.