Triple
T3992714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Household Ceremonial Team |
E87028
|
entity |
| Predicate | eventTypeHandled |
P17506
|
FINISHED |
| Object | state visits |
—
|
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: state visits | Statement: [Royal Household Ceremonial Team, eventTypeHandled, state visits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventTypeHandled Context triple: [Royal Household Ceremonial Team, eventTypeHandled, state visits]
-
A.
dealtWithEvent
chosen
Indicates that an entity has handled, responded to, or otherwise taken action to address a particular event.
-
B.
eventCommanded
Indicates that one entity issued an order or directive for another entity to carry out a specific event or action.
-
C.
eventContext
Indicates the situational or background circumstances (such as time, place, conditions, or surrounding events) within which a particular event occurs or is interpreted.
-
D.
facedEvent
Indicates that an entity directly encountered, experienced, or dealt with a particular event.
-
E.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
- 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_69aed94118148190975e6aa4e554cde9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.