Triple
T13781826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Masters |
E331148
|
entity |
| Predicate | reintroducedAsRankingEvent |
P111442
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [German Masters, reintroducedAsRankingEvent, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reintroducedAsRankingEvent Context triple: [German Masters, reintroducedAsRankingEvent, 2011]
-
A.
typeOfRankingEvent
Indicates the specific kind or category of ranking-related event that is being referred to.
-
B.
reintroducedAsTier
Indicates that something has been brought back or reinstated in a system or structure as a specific tier or level.
-
C.
formerRankingSystem
Indicates that a ranking system previously used in a given context is no longer current or in effect.
-
D.
isRanked
Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
-
E.
formerRanking
Indicates that an entity previously held a particular rank or position but no longer does so.
- F. None of above. chosen
Provenance (4 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02460a688190a27874f8d35819c7 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:11 p.m.