Triple
T34672857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.I. Robot |
E890421
|
entity |
| Predicate | isCyborg |
P179603
|
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: [G.I. Robot, isCyborg, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCyborg Context triple: [G.I. Robot, isCyborg, false]
-
A.
hasCybernetic
Indicates that an entity possesses or is equipped with cybernetic enhancements, implants, or components.
-
B.
featuresCyborg
Indicates that something includes or prominently presents a cyborg as part of its content or composition.
-
C.
hasExoskeleton
Indicates that an entity possesses an external supportive or protective skeletal structure covering its body.
-
D.
relationshipToCyborg
Indicates the type or nature of a person's relational connection to a cyborg, such as familial, social, or professional.
-
E.
roleInCyborgOrigin
Indicates that an entity plays a specific role in the origin, creation, or transformation process that results in a cyborg.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7232166488190939c02bdaeacb490 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: May 1, 2026, 2:05 a.m.