Triple
T1718969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Control Panel |
E37349
|
entity |
| Predicate | allowsConfigurationOf |
P273
|
FINISHED |
| Object | system settings |
—
|
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: system settings | Statement: [Control Panel, allowsConfigurationOf, system settings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsConfigurationOf Context triple: [Control Panel, allowsConfigurationOf, system settings]
-
A.
allows
chosen
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
B.
allowsRegulationOf
Indicates that one entity grants the authority, means, or conditions for another entity to control, manage, or govern something.
-
C.
allowedReturn
Indicates that an entity is permitted to be returned or sent back under specified conditions or rules.
-
D.
hasConfiguration
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
E.
canOverrule
Indicates that one entity has the authority or power to reverse, nullify, or supersede the decision or judgment made by 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab5c96db6c8190a745d6fef7bf2cdb |
completed | March 6, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69aa61bed2fc819086d912cd34285978 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.