Triple
T4506635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyborg |
E101345
|
entity |
| Predicate | bodyComposition |
P50920
|
FINISHED |
| Object | part human part machine |
—
|
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: part human part machine | Statement: [Cyborg, bodyComposition, part human part machine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyComposition Context triple: [Cyborg, bodyComposition, part human part machine]
-
A.
primaryBodyType
chosen
Indicates the main physical form or category that characterizes an entity’s overall body structure or composition.
-
B.
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.
-
C.
bodyContour
Indicates the shape or outline of a body as defined by its external curves and boundaries.
-
D.
residesOverBodyType
Indicates that one entity is positioned or located above another entity that is characterized by a specific body type.
-
E.
bodySegmentation
Indicates a relationship where an entity is divided or delineated into distinct anatomical or structural body segments.
- 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd570e7bb8819097f7a575384a10a8 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd5218afb4819087c99e0a1f22e137 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:01 p.m.