Triple
T29247988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3DO |
E741487
|
entity |
| Predicate | controllerDaisyChainSupport |
P105949
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [3DO, controllerDaisyChainSupport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controllerDaisyChainSupport Context triple: [3DO, controllerDaisyChainSupport, yes]
-
A.
maximumDaisyChainedDevices
chosen
Indicates the maximum number of devices that can be connected in a daisy-chain configuration within the specified context.
-
B.
controlLink
Indicates a relationship where one entity exerts control, influence, or governing authority over another entity or process.
-
C.
hasLinkCableSupport
Indicates that one entity supports being connected to another via a link cable for interaction or data exchange.
-
D.
canBeControlledFrom
Indicates that one entity has the ability or authority to operate, direct, or manage another entity remotely or indirectly.
-
E.
controlFeatures
Indicates that one entity has the ability to configure, manage, or influence the operational settings or characteristics of another entity.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 28, 2026, 12:33 p.m.