Triple
T6649283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarina Wiegman |
E150777
|
entity |
| Predicate | reasonForCBE |
P24494
|
FINISHED |
| Object | services to football |
—
|
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: services to football | Statement: [Sarina Wiegman, reasonForCBE, services to football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForCBE Context triple: [Sarina Wiegman, reasonForCBE, services to football]
-
A.
statedReason
chosen
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
B.
reasonForUse
Indicates that one entity specifies the justification, purpose, or motivation for using another entity.
-
C.
reasonForEvent
Indicates that one event occurs as a consequence of, or is motivated or explained by, another specified cause or reason.
-
D.
selectionReason
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
E.
reasonForSpecialMeasures
Indicates that one entity specifies the justification or cause for which special measures or exceptional actions are taken regarding another entity.
- 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:01 p.m.