Triple
T34286964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allen |
E879764
|
entity |
| Predicate | controlSystemType |
P17356
|
FINISHED |
| Object | layered control system |
—
|
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: layered control system | Statement: [Allen, controlSystemType, layered control system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlSystemType Context triple: [Allen, controlSystemType, layered control system]
-
A.
controlsSystem
Indicates that one entity has the authority or capability to direct, manage, or regulate the operation of a system.
-
B.
controlsServiceType
Indicates that one entity has authority to manage, regulate, or determine the operation or availability of a particular type of service.
-
C.
controlsType
Indicates that one entity has authority over, or the ability to direct or regulate, the type or category of another entity.
-
D.
controlUnitType
chosen
Indicates the specific kind or category of control unit associated with or assigned to an entity.
-
E.
controlsDeviceType
Indicates that an entity has authority over or can operate a specific type or category of device.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: May 1, 2026, 1:57 a.m.