Triple
T17747938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rossum Corporation |
E443034
|
entity |
| Predicate | hiddenActivity |
P115847
|
FINISHED |
| Object | illegal human experimentation |
—
|
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: illegal human experimentation | Statement: [Rossum Corporation, hiddenActivity, illegal human experimentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hiddenActivity Context triple: [Rossum Corporation, hiddenActivity, illegal human experimentation]
-
A.
hiddenIn
Indicates that one entity is concealed within, behind, or inside another entity so that it is not readily visible or apparent.
-
B.
protectedActivity
Indicates that an entity is engaged in an action or behavior that is legally or formally safeguarded from retaliation, interference, or adverse consequences.
-
C.
hiddenAt
Indicates that one entity is concealed or stored at a specific location or within another entity.
-
D.
secretedBy
Indicates that a substance or product is released or produced by a particular cell, tissue, organ, or organism.
-
E.
hiddenLife
chosen
Indicates that an entity has aspects, activities, or a mode of existence that are concealed or not openly known to others.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47ad46a50819089c87f74efe3c7ca |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:10 a.m.