Triple
T5971674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meg Altman |
E132888
|
entity |
| Predicate | threatFaced |
P50110
|
FINISHED |
| Object | home invasion by burglars |
—
|
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: home invasion by burglars | Statement: [Meg Altman, threatFaced, home invasion by burglars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatFaced Context triple: [Meg Altman, threatFaced, home invasion by burglars]
-
A.
threat
Indicates a relationship where one entity expresses or poses potential harm, danger, or negative consequences toward another entity.
-
B.
threatType
chosen
Indicates the specific category or nature of a threat that one entity poses or represents in relation to another.
-
C.
threatStatus
Indicates the level or category of risk or danger posed by one entity to another or to a defined system or environment.
-
D.
threatTypeEngaged
Indicates that an entity has actively engaged with or responded to a specific type of threat.
-
E.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
- 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_69c0086deab081908550159ca23eec9b |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc2243c8190bd3488e7b24af985 |
completed | March 22, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c049dcb3c081908ccc9b4d4b210229 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:03 p.m.