Triple
T32561934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Tour Order of Merit |
E832249
|
entity |
| Predicate | topPositionLabel |
P136302
|
FINISHED |
| Object | Order of Merit winner |
—
|
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: Order of Merit winner | Statement: [European Tour Order of Merit, topPositionLabel, Order of Merit winner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topPositionLabel Context triple: [European Tour Order of Merit, topPositionLabel, Order of Merit winner]
-
A.
topLocation
Indicates that one location is the primary, highest-level, or most prominent place associated with another entity or set of locations.
-
B.
topPositionHeldBy
Indicates that a particular top or highest-ranking position is occupied or held by a specific entity.
-
C.
topHas
Indicates that one entity possesses, contains, or is associated with another entity at the highest or most general level in a hierarchy or structure.
-
D.
topBoundary
Indicates that one entity serves as the uppermost limit, edge, or border of another entity or region.
-
E.
highestLevelLabel
chosen
Indicates the most specific or top-priority label assigned to an entity within a hierarchy or labeling 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c6084a348190a1b644c398d91589 |
completed | May 3, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:03 a.m.