Triple
T16988005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish women's football league system |
E412119
|
entity |
| Predicate | tier1NumberOfDivisions |
P52754
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Scottish women's football league system, tier1NumberOfDivisions, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tier1NumberOfDivisions Context triple: [Scottish women's football league system, tier1NumberOfDivisions, 2]
-
A.
topLevelDivisionCount
chosen
Indicates the number of primary administrative or organizational divisions directly under a given entity.
-
B.
typicalNumberOfTopDivisionTeams
Indicates the usual or standard number of teams that compete in the highest-level division of a league or competition.
-
C.
tierOfDivisionIA
Indicates that one entity is classified as a Division I-A (top-tier) level within a tiered divisional structure.
-
D.
topDivisionLevel
Indicates that an entity belongs to the highest or primary division level within a hierarchical or organizational structure.
-
E.
topLevelDivisions
Indicates that one administrative or organizational unit is a primary, highest-level subdivision within a larger entity or system.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d27cd2048190800a60ae653e11e1 |
completed | April 18, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69e35d4dff4881909b384e30f2d36bff |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:32 a.m.