Triple
T37476858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-23 |
E931303
|
entity |
| Predicate | isUsedInControlCenterSystems |
P188377
|
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: [A-23, isUsedInControlCenterSystems, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedInControlCenterSystems Context triple: [A-23, isUsedInControlCenterSystems, true]
-
A.
utilitiesControlledBy
Indicates that one entity has authority over, management of, or operational control of another entity’s utilities or utility services.
-
B.
canBeControlledFrom
Indicates that one entity has the ability or authority to operate, direct, or manage another entity remotely or indirectly.
-
C.
hasCentralUnit
Indicates that an entity possesses or is associated with a primary controlling or coordinating unit.
-
D.
isPartOfAccessSystem
Indicates that something functions as a component or element within a larger access control or access management system.
-
E.
operatesUnderControlOf
Indicates that one entity functions or carries out its activities subject to the authority, direction, or governance of another entity.
- F. None of above. chosen
Provenance (4 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba67f78348190ab160988e4698394 |
completed | May 6, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.