Triple
T2682482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bowl Alliance |
E57403
|
entity |
| Predicate | usedRankingSystem |
P12770
|
FINISHED |
| Object | poll rankings |
—
|
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: poll rankings | Statement: [Bowl Alliance, usedRankingSystem, poll rankings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedRankingSystem Context triple: [Bowl Alliance, usedRankingSystem, poll rankings]
-
A.
usesRank
chosen
Indicates that one entity applies or relies on a ranking or ordered level system associated with another entity.
-
B.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
-
C.
hasOfficialRankingSystem
Indicates that there exists a formally recognized and structured system for ranking or ordering entities according to defined criteria.
-
D.
usesRankStructure
Indicates that an entity organizes its members or components according to a defined hierarchical rank structure.
-
E.
formerRanking
Indicates that an entity previously held a particular rank or position but no longer does so.
- 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9d602848190b638e417e710a555 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.