Triple
T26774401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Swinton |
E670076
|
entity |
| Predicate | inUniverseTechnologyContext |
P74633
|
FINISHED |
| Object | mecha (robots) |
—
|
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: mecha (robots) | Statement: [Henry Swinton, inUniverseTechnologyContext, mecha (robots)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseTechnologyContext Context triple: [Henry Swinton, inUniverseTechnologyContext, mecha (robots)]
-
A.
inUniverseTechnologyOf
Indicates that a technology exists within, and is part of, the fictional universe or setting associated with a given entity.
-
B.
inUniverseTechnologyDeveloped
Indicates that a specific technology has been created or developed within the context of a particular fictional or defined universe.
-
C.
technologyContext
chosen
Indicates the technological setting, tools, or systems within which an action, relationship, or process occurs.
-
D.
inUniverseUse
Indicates that something is used or occurs within a particular fictional or conceptual universe, as opposed to in the real world or another setting.
-
E.
technologyAgnostic
Indicates that something is designed or functions independently of any specific technology, platform, or vendor, and can work with multiple technological options.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 4:03 a.m.