Triple
T36697643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terrigen Mists |
E906133
|
entity |
| Predicate | activationProcess |
P164199
|
FINISHED |
| Object | Terrigenesis |
—
|
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: Terrigenesis | Statement: [Terrigen Mists, activationProcess, Terrigenesis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activationProcess Context triple: [Terrigen Mists, activationProcess, Terrigenesis]
-
A.
activationBy
chosen
Indicates that one entity initiates, triggers, or enhances the activity, function, or state of another entity.
-
B.
activationType
Indicates the specific manner or mechanism by which an activation or triggering event occurs between entities.
-
C.
activationNetwork
Indicates that one entity initiates, enhances, or enables the functional activity of another entity within a connected system or pathway.
-
D.
activationBlock
Indicates that one entity prevents or inhibits the activation or functioning of another entity.
-
E.
activatedAs
Indicates that one entity has been put into an active or operational state in the role or capacity of another specified 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.