Triple
T22924445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Runaway Robot |
E569260
|
entity |
| Predicate | hasRobotProtagonist |
P84658
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Runaway Robot, hasRobotProtagonist, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRobotProtagonist Context triple: [The Runaway Robot, hasRobotProtagonist, true]
-
A.
hasRobotDesignationForProtagonist
Indicates that an entity serves as the specific robot designation or identifier assigned to the protagonist.
-
B.
hasRobotCharacterRole
chosen
Indicates that an entity participates in a role or function specifically as a robot character within a given context or work.
-
C.
hasInspectorProtagonist
Indicates that the main character in the work serves in the role of an inspector.
-
D.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
E.
hasRobot
Indicates that one entity possesses, controls, or is associated with a robot.
- 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180d84fc08190b747c3f9052c657a |
completed | April 29, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:43 p.m.