Triple
T36812858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karnak |
E909641
|
entity |
| Predicate | underwentTerrigenesis |
P85351
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Karnak, underwentTerrigenesis, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underwentTerrigenesis Context triple: [Karnak, underwentTerrigenesis, false]
-
A.
terraformedBy
Indicates that an environment, planet, or celestial body has been altered or engineered to be more Earth-like by a specified agent or process.
-
B.
wasTransformedBy
chosen
Indicates that an entity has undergone a change of state, form, or condition as the result of an action, process, or agent.
-
C.
geneticallyManipulatedBy
Indicates that an entity’s genetic material has been altered or modified as a result of actions performed by another specified agent or process.
-
D.
evolvedUnder
Indicates that one entity developed or changed over time while being influenced or shaped by specific conditions, factors, or an environment represented by the other entity.
-
E.
regenerationAbility
Indicates the capability of an entity to restore or regrow lost or damaged parts of itself.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: May 3, 2026, 4:13 p.m.