Triple
T32561918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Tour Order of Merit |
E832249
|
entity |
| Predicate | successorSystemIntroduced |
P88961
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [European Tour Order of Merit, successorSystemIntroduced, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorSystemIntroduced Context triple: [European Tour Order of Merit, successorSystemIntroduced, 2009]
-
A.
successorSystem
Indicates that one system directly follows and replaces another in function, role, or version.
-
B.
introducedAsSuccessorOf
chosen
Indicates that one entity was formally presented or designated to take over the role, position, or function previously held by another entity.
-
C.
successorStructureIntroducedIn
Indicates that a particular successor structure was first introduced or defined in a specified source, context, or work.
-
D.
successorManufacturer
Indicates that one manufacturer has taken over, replaced, or continued the role or operations of another manufacturer as its successor.
-
E.
successorEngineFamily
Indicates that one engine family directly follows and replaces another in a product or development lineage.
- 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_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: May 1, 2026, 1:03 a.m.