Triple
T8493014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liar! |
E201018
|
entity |
| Predicate | centralTechnology |
P38305
|
FINISHED |
| Object | mind-reading robot |
—
|
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: mind-reading robot | Statement: [Liar!, centralTechnology, mind-reading robot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralTechnology Context triple: [Liar!, centralTechnology, mind-reading robot]
-
A.
technologyBasis
chosen
Indicates that one entity is founded on, enabled by, or fundamentally relies upon the technology provided or represented by another entity.
-
B.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
C.
technologicalFeature
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to another entity.
-
D.
technologyConcept
Indicates a relationship where one entity represents or embodies a technological idea, principle, or method conceptually associated with another entity.
-
E.
technologyLevel
Indicates the degree of technological advancement or sophistication associated with an entity relative to others or to a defined scale.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe579b7088190b297b04527e36a2b |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.