Triple
T28019965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LGB |
E707657
|
entity |
| Predicate | controlOption |
P123498
|
FINISHED |
| Object | analog control |
—
|
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: analog control | Statement: [LGB, controlOption, analog control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlOption Context triple: [LGB, controlOption, analog control]
-
A.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
B.
controlParameter
chosen
Indicates that one entity functions as a parameter that governs, tunes, or constrains the behavior or operation of another entity.
-
C.
controlApp
Indicates that one entity has the ability or authority to operate, manage, or direct the behavior of an application.
-
D.
settingOfControl
Indicates that one entity is the context or environment in which another entity exercises control or governance.
-
E.
controlsType
Indicates that one entity has authority over, or the ability to direct or regulate, the type or category of 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 27, 2026, 8:09 p.m.