Triple
T26680492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Fagan |
E672593
|
entity |
| Predicate | intruded |
P73806
|
FINISHED |
| Object | Buckingham Palace |
—
|
NE NERFINISHED |
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: Buckingham Palace | Statement: [Michael Fagan, intruded, Buckingham Palace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intruded Context triple: [Michael Fagan, intruded, Buckingham Palace]
-
A.
intrudedInto
chosen
Indicates that one entity has entered or encroached upon another entity’s space, domain, or context without permission or in an unwelcome manner.
-
B.
infiltratedBy
Indicates that an entity has been secretly entered, penetrated, or taken over by another entity, typically in a covert or unauthorized manner.
-
C.
invade
Indicates entering another entity’s territory or domain, typically by force or without permission, in order to take control or exert dominance.
-
D.
impregnatedBy
Indicates that one entity has caused another entity to become pregnant.
-
E.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
- 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_69f617074dcc819099bbeeb8f1b49dd7 |
completed | May 2, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:19 a.m.