Triple
T26680493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Fagan |
E672593
|
entity |
| Predicate | intrusionYear |
P161604
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [Michael Fagan, intrusionYear, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intrusionYear Context triple: [Michael Fagan, intrusionYear, 1982]
-
A.
investigationYear
Indicates the specific calendar year in which an investigation takes place or is formally conducted.
-
B.
wasAttackedInYear
Indicates that an entity was the target of an attack that occurred in the specified year.
-
C.
intrusionStyle
Indicates the characteristic manner or method by which an intrusion or unauthorized access is carried out.
-
D.
yearOfInsertion
Indicates the calendar year in which an entity was added, introduced, or inserted into a particular system, collection, or context.
-
E.
majorIntrusionAge
Indicates the age at which a major intrusive geological event (such as a significant igneous intrusion) occurred relative to the referenced entity.
- F. None of above. chosen
Provenance (4 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_69f61ad613608190855de13501a86007 |
completed | May 2, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f61a16b7848190bf20d2be7e5a16c1 |
completed | May 2, 2026, 3:36 p.m. |
Created at: April 27, 2026, 3:19 a.m.