Triple
T31453055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIH Pro League |
E802374
|
entity |
| Predicate | confersRankingPoints |
P167929
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [FIH Pro League, confersRankingPoints, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confersRankingPoints Context triple: [FIH Pro League, confersRankingPoints, true]
-
A.
hasRankingPoints
Indicates that an entity possesses a certain number of ranking points used to determine its position or standing within a ranking system.
-
B.
rankingPointsAwardedBy
Indicates the number of ranking points granted by a particular source or authority to an entity.
-
C.
usesRankingPoints
chosen
Indicates that one entity bases its ordering, evaluation, or decision-making on ranking points associated with another entity.
-
D.
rankingPoints
Indicates the number of points assigned to an entity based on its position or performance in a ranking or competition.
-
E.
pointsAwarded
Indicates that a specified number of points has been granted to an entity as a result of some action or event.
- 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: April 30, 2026, 9:14 p.m.