Triple
T33727527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Real Transported Man |
E864183
|
entity |
| Predicate | involvesDevice |
P9919
|
FINISHED |
| Object | Tesla’s machine |
—
|
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: Tesla’s machine | Statement: [The Real Transported Man, involvesDevice, Tesla’s machine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesDevice Context triple: [The Real Transported Man, involvesDevice, Tesla’s machine]
-
A.
relatedToDevice
Indicates that there exists a general association or connection between an entity and a device, without specifying the exact nature of that relationship.
-
B.
occursInDevice
Indicates that an event, process, or phenomenon takes place within or inside a specified device.
-
C.
includesDevices
Indicates that one entity contains, encompasses, or has as part of it one or more devices.
-
D.
usesDevice
chosen
Indicates that one entity operates, employs, or relies on a particular device to perform an action or achieve a purpose.
-
E.
relatedDevice
Indicates that one device has an association or connection to another device, without specifying the exact nature of that relationship.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 1, 2026, 1:44 a.m.