Triple
T2134827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penny Mordaunt |
E46624
|
entity |
| Predicate | roleAtEvent |
P4073
|
FINISHED |
| Object | carried the Sword of State at the coronation of King Charles III |
—
|
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: carried the Sword of State at the coronation of King Charles III | Statement: [Penny Mordaunt, roleAtEvent, carried the Sword of State at the coronation of King Charles III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtEvent Context triple: [Penny Mordaunt, roleAtEvent, carried the Sword of State at the coronation of King Charles III]
-
A.
eventRole
chosen
Indicates the specific function, capacity, or part an entity plays within an event or occurrence.
-
B.
eventParticipant
Indicates that an entity takes part in, is involved in, or participates in a particular event.
-
C.
participatedInEvent
Indicates that an entity took part in or was actively involved in a specific event.
-
D.
partOfEvent
Indicates that one entity is a component, segment, or sub-activity that belongs to or occurs within a larger event.
-
E.
significantEventRole
Indicates that an entity plays an important or defining role in a particular significant event.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbba24004819091ffb9440e8615fa |
completed | March 7, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69abb7bf56e481909b0f497d238451cc |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.