Triple
T6991854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inferno |
E162102
|
entity |
| Predicate | namespacePerProcess |
P74327
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Inferno, namespacePerProcess, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namespacePerProcess Context triple: [Inferno, namespacePerProcess, yes]
-
A.
usedProcess
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
B.
definesProcessFor
Indicates that one entity specifies or establishes the process or procedure to be used for another entity.
-
C.
namespace
Indicates a scoping relationship in which identifiers or symbols are grouped under a specific context or name to avoid conflicts and organize them.
-
D.
dominantProcess
Indicates that one process exerts primary control or influence over another process within a given context.
-
E.
processType
Indicates the specific kind or category of process that an entity or activity belongs to.
- 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc1f63c8190837cfd71cf5ed613 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6dbbc00fc8190a18221524b774021 |
completed | March 27, 2026, 7:34 p.m. |
Created at: March 27, 2026, 2:32 p.m.