Triple
T26105252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rome |
E658518
|
entity |
| Predicate | coreDieProcessNode |
P159952
|
FINISHED |
| Object | 7 nm |
—
|
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: 7 nm | Statement: [Rome, coreDieProcessNode, 7 nm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreDieProcessNode Context triple: [Rome, coreDieProcessNode, 7 nm]
-
A.
keyProcessNode
Indicates that one node in a process or workflow is designated as a primary or critical step relative to the overall process structure.
-
B.
processNode
Indicates performing an operation or series of operations on a node within a data structure or system.
-
C.
killedDuring
Indicates that one entity caused the death of another entity in the course of, or as part of, a specified event or time period.
-
D.
diesBy
Indicates that one entity causes or is responsible for the death of another entity.
-
E.
intendedProcessNode
Indicates that one entity is designated or planned to serve as the process node for another entity within a process or workflow.
- 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_69ee5bc09c288190bc42a11972841383 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60775b298819095c64aca6806d61c |
completed | May 2, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 7:58 p.m.