Triple
T10321257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moroccan Throne Cup |
E242142
|
entity |
| Predicate | deciderOf |
P93361
|
FINISHED |
| Object | national cup champion of Morocco |
—
|
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: national cup champion of Morocco | Statement: [Moroccan Throne Cup, deciderOf, national cup champion of Morocco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deciderOf Context triple: [Moroccan Throne Cup, deciderOf, national cup champion of Morocco]
-
A.
decider
Indicates that an entity is the one who makes a choice or decision in a given situation or process.
-
B.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
-
C.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
D.
wasDecidedBy
Indicates that a decision or outcome was determined or resolved by a specific agent or authority.
-
E.
decidedWith
Indicates that an entity made a decision jointly or in agreement with another entity.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7ccb7ec8190a538cf279e48116e |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f64a648190a79980d647898eb0 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d7cada7881908beba55a1dc9ecb9 |
completed | April 7, 2026, 10:09 a.m. |
Created at: April 6, 2026, 11:50 a.m.