Triple
T8535048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silas Stone |
E202056
|
entity |
| Predicate | relationshipToCyborg |
P83185
|
FINISHED |
| Object | estranged father in many storylines |
—
|
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: estranged father in many storylines | Statement: [Silas Stone, relationshipToCyborg, estranged father in many storylines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToCyborg Context triple: [Silas Stone, relationshipToCyborg, estranged father in many storylines]
-
A.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
B.
featuresCyborg
Indicates that something includes or prominently presents a cyborg as part of its content or composition.
-
C.
hasCybernetic
Indicates that an entity possesses or is equipped with cybernetic enhancements, implants, or components.
-
D.
relationshipToMother
Indicates the specific familial or social connection an entity has to its mother.
-
E.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
- 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6a295c88190a432a060ee73f04e |
completed | March 31, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:17 p.m.