Triple
T8492621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fallom |
E201008
|
entity |
| Predicate | hasBodyModification |
P61330
|
FINISHED |
| Object | Solarian genetic engineering background |
—
|
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: Solarian genetic engineering background | Statement: [Fallom, hasBodyModification, Solarian genetic engineering background]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBodyModification Context triple: [Fallom, hasBodyModification, Solarian genetic engineering background]
-
A.
hasBodySwapWith
Indicates a reciprocal relationship where two entities have exchanged bodies or physical forms with each other.
-
B.
hasHumanModification
chosen
Indicates that an entity has been altered, influenced, or modified as a result of human activity or intervention.
-
C.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
-
D.
usesBodyPart
Indicates that an entity performs an action or function by employing a specific body part as a means or tool.
-
E.
belongsToBody
Indicates that something is a part of, or under the ownership/authority of, a particular body or organization.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe55cf5dc81908cad31ac53e15b46 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.