Triple
T18998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oppenheimer–Phillips process |
E375
|
entity |
| Predicate | involvesTarget |
P860
|
FINISHED |
| Object | atomic nucleus |
—
|
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: atomic nucleus | Statement: [Oppenheimer–Phillips process, involvesTarget, atomic nucleus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesTarget Context triple: [Oppenheimer–Phillips process, involvesTarget, atomic nucleus]
-
A.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
B.
target
chosen
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
C.
involvedUnit
Indicates that a particular unit (such as a group, organization, or division) participates in, is associated with, or plays a role in the referenced event or activity.
-
D.
primaryTarget
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
-
E.
chamberInvolved
Indicates that a particular chamber (e.g., legislative or judicial body) participates in, is affected by, or plays a role in the referenced event, process, or relationship.
- 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_69a240778d288190815c0052ebbbcc91 |
completed | Feb. 28, 2026, 1:10 a.m. |
| NER | Named-entity recognition | batch_69a246cbca108190a92478df126d9bf8 |
completed | Feb. 28, 2026, 1:37 a.m. |
| PD | Predicate disambiguation | batch_69a2464f61648190ac690044be194972 |
completed | Feb. 28, 2026, 1:35 a.m. |
Created at: Feb. 28, 2026, 1:14 a.m.