Triple
T11305869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PTP |
E267710
|
entity |
| Predicate | allowsOperation |
P31805
|
FINISHED |
| Object | remote control of camera functions |
—
|
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: remote control of camera functions | Statement: [PTP, allowsOperation, remote control of camera functions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsOperation Context triple: [PTP, allowsOperation, remote control of camera functions]
-
A.
canOperateAt
Indicates that one entity has the capability, permission, or suitability to function or perform its role at, within, or under the conditions of another entity or context.
-
B.
supportsOperationsIn
Indicates that one entity enables, facilitates, or backs the execution of operations within a specified context, area, or domain of another entity.
-
C.
canOperateUnder
Indicates that one entity is permitted, able, or qualified to function, perform, or remain active within the conditions, authority, or environment defined by another entity.
-
D.
mayBeOperatedBy
Indicates that an entity has the potential or permission to be operated, controlled, or run by another entity.
-
E.
operationSupported
chosen
Indicates that a particular operation is available and can be performed or handled by a given entity or system.
- 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9a7255c81909675fe9ad6d71934 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.