Triple
T30350703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony WI-C310 |
E771980
|
entity |
| Predicate | controlLocation |
P138426
|
FINISHED |
| Object | in-line remote on cable |
—
|
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: in-line remote on cable | Statement: [Sony WI-C310, controlLocation, in-line remote on cable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlLocation Context triple: [Sony WI-C310, controlLocation, in-line remote on cable]
-
A.
controlsLocation
Indicates that one entity has authority over, manages, or determines the status or use of a particular location.
-
B.
locationOfControl
Indicates that one entity is the place or context in which another entity exercises authority, management, or control.
-
C.
typicalControlLocation
chosen
Indicates the usual or standard physical location from which control or operation of something is exercised.
-
D.
controlDirection
Indicates that one entity exerts influence or guidance over the orientation, course, or movement direction of another entity.
-
E.
controlContext
Indicates that one entity governs, constrains, or determines the conditions under which another entity operates or is interpreted.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 29, 2026, 7:56 p.m.