Triple
T35281445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sub 37 |
E1018942
|
entity |
| Predicate | hasPerformanceControls |
P54506
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sub 37, hasPerformanceControls, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformanceControls Context triple: [Sub 37, hasPerformanceControls, true]
-
A.
controlFeatures
Indicates that one entity has the ability to configure, manage, or influence the operational settings or characteristics of another entity.
-
B.
controlsFeaturesAt
Indicates that one entity has the authority or capability to manage, configure, or influence specific features at a particular location or context.
-
C.
supportsSpeedControls
chosen
Indicates that an entity provides or is compatible with mechanisms to adjust or control speed.
-
D.
hasPerformanceElement
Indicates that one entity includes, contains, or is associated with a specific performance-related component or element.
-
E.
hasPerformanceProfile
Indicates that an entity is associated with a specific performance profile that characterizes its performance attributes or behavior.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.