Triple
T36235805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1889–90 Football League season |
E891374
|
entity |
| Predicate | tableRankingMethod |
P12242
|
FINISHED |
| Object | points total |
—
|
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: points total | Statement: [1889–90 Football League season, tableRankingMethod, points total]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tableRankingMethod Context triple: [1889–90 Football League season, tableRankingMethod, points total]
-
A.
hasTableRanking
Indicates that an entity is assigned a specific position or order within a ranked table or list.
-
B.
rankingPositions
Indicates the ordered placement or level assigned to entities within a ranking or hierarchy.
-
C.
rankingType
chosen
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
D.
selectionRankingEndPoint
Indicates the position or boundary in an ordered list at which a selection or ranking process concludes.
-
E.
hasRankingAlgorithm
Indicates that an entity uses or is associated with a specific algorithm for ranking or ordering items.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5a656808190b77b60d4703d0d91 |
completed | May 3, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.