Triple
T29083076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halfworld |
E734029
|
entity |
| Predicate | modificationOfInhabitants |
P165981
|
FINISHED |
| Object | genetically engineered |
—
|
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: genetically engineered | Statement: [Halfworld, modificationOfInhabitants, genetically engineered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modificationOfInhabitants Context triple: [Halfworld, modificationOfInhabitants, genetically engineered]
-
A.
fateOfInhabitants
Indicates the outcome or destiny that befalls the inhabitants of a place or group, such as survival, displacement, or death.
-
B.
movementOfSpecies
Indicates the relocation or spread of a species from one place or region to another over time.
-
C.
inhabitedBy
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
D.
originalInhabitant
Indicates that an entity was among the first or earliest residents of a particular place or territory.
-
E.
hasMotiveForInhabitants
Indicates that an entity provides or embodies a reason, incentive, or justification for the actions, behaviors, or presence of its inhabitants.
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6614566d88190aa5973e73819cf18 |
completed | May 2, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65ad638ac8190a17bb987fce53279 |
completed | May 2, 2026, 8:13 p.m. |
Created at: April 28, 2026, 10:57 a.m.