Triple
T26680503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Fagan |
E672593
|
entity |
| Predicate | eventClassification |
P7504
|
FINISHED |
| Object | royal security breach |
—
|
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: royal security breach | Statement: [Michael Fagan, eventClassification, royal security breach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventClassification Context triple: [Michael Fagan, eventClassification, royal security breach]
-
A.
eventName
Indicates the specific label or title assigned to identify an event within a system or context.
-
B.
calendarCategory
Indicates the classification or grouping assigned to calendar entries based on their type, purpose, or context.
-
C.
typeOfEvent
chosen
Indicates that one entity is classified as a specific kind or category of event.
-
D.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
E.
classificationStart
Indicates the point in time or process at which a classification or categorization of an entity begins.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 3:19 a.m.