Triple
T14238665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nestene Consciousness |
E352951
|
entity |
| Predicate | bodilyForm |
P50920
|
FINISHED |
| Object | disembodied |
—
|
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: disembodied | Statement: [Nestene Consciousness, bodilyForm, disembodied]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodilyForm Context triple: [Nestene Consciousness, bodilyForm, disembodied]
-
A.
usesBodyPart
Indicates that an entity performs an action or function by employing a specific body part as a means or tool.
-
B.
bodyFusedWith
Indicates that two or more bodies or physical structures are joined together into a single, continuous unit.
-
C.
parentBodyType
Indicates that one entity has a body type that serves as the parent or base classification from which another entity's body type is derived or organized.
-
D.
primaryBodyType
chosen
Indicates the main physical form or category that characterizes an entity’s overall body structure or composition.
-
E.
supportingBody
Indicates that one entity serves as a supporting or backing body for another entity, providing endorsement, resources, or structural support.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de62432fb48190b153805b85c4f2d2 |
completed | April 14, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69de05bf069c8190b69f00f00f5eb126 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:08 a.m.