Triple
T19646910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drax Industries |
E471697
|
entity |
| Predicate | frontFor |
P48734
|
FINISHED |
| Object | Hugo Drax's genocidal plan |
—
|
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: Hugo Drax's genocidal plan | Statement: [Drax Industries, frontFor, Hugo Drax's genocidal plan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontFor Context triple: [Drax Industries, frontFor, Hugo Drax's genocidal plan]
-
A.
frontOf
Indicates that one entity is positioned directly before another along a primary viewing or movement direction.
-
B.
front
Indicates that one entity is located directly before or facing another entity along a primary viewing or movement direction.
-
C.
frontType
Indicates the type or category of a front (e.g., boundary or leading side) that one entity presents or forms relative to another.
-
D.
frontEndFor
Indicates that one entity serves as the user-facing interface or access point through which another underlying system, service, or component is used or interacted with.
-
E.
frontPerson
chosen
Indicates that one entity serves as the primary representative, leader, or public face positioned at the forefront in relation to another entity.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e64125dd9481908a891c71c975a964 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.