Triple
T22775125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish football pyramid |
E563673
|
entity |
| Predicate | thirdTierNumberOfClubs |
P149680
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Scottish football pyramid, thirdTierNumberOfClubs, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdTierNumberOfClubs Context triple: [Scottish football pyramid, thirdTierNumberOfClubs, 10]
-
A.
thirdTierNumberOfDivisions
Indicates the number of organizational or structural divisions that exist at the third hierarchical tier within a larger system.
-
B.
thirdTier
Indicates that an entity occupies a third level or rank within a hierarchical structure or classification.
-
C.
typicalNumberOfClubs
Indicates the usual or most common number of clubs associated with an entity in a given context.
-
D.
secondDivisionNumberOfClubs
Indicates the total number of clubs that participate in the second division of a competition or league.
-
E.
hasThirdDivision
Indicates that an entity possesses or is associated with a third-level division or subdivision within a hierarchical structure.
- F. None of above. chosen
Provenance (4 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_69e24554497c819080b996e071de27c2 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b60eec48190b0aaf3eb7ede38d4 |
completed | April 29, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:28 p.m.