Triple
T6446749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Tour |
E138360
|
entity |
| Predicate | usesRankingFor |
P12770
|
FINISHED |
| Object | season-long points list |
—
|
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: season-long points list | Statement: [European Tour, usesRankingFor, season-long points list]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRankingFor Context triple: [European Tour, usesRankingFor, season-long points list]
-
A.
usesRank
chosen
Indicates that one entity applies or relies on a ranking or ordered level system associated with another entity.
-
B.
usesRankStructure
Indicates that an entity organizes its members or components according to a defined hierarchical rank structure.
-
C.
hasRankingFactor
Indicates that one entity contributes as a factor to determining the ranking or ordered position of another entity.
-
D.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
-
E.
usesRankStructureSimilarTo
Indicates that one entity organizes or orders its elements according to a ranking system that is similar to the ranking system used by another entity.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0698edeac81909426902471d8a57b |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c0673b44148190aed70084f0ff4992 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:46 p.m.