Triple
T6328046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Analytical Engine |
E141905
|
entity |
| Predicate | controlMedium |
P70878
|
FINISHED |
| Object | mechanical gears and levers |
—
|
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: mechanical gears and levers | Statement: [Analytical Engine, controlMedium, mechanical gears and levers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlMedium Context triple: [Analytical Engine, controlMedium, mechanical gears and levers]
-
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.
canControl
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
-
C.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
-
D.
controlStatus
Indicates that one entity has a particular level, state, or condition of control over another entity or process.
-
E.
controlled
Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064e9532081908277f10ec380a486 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c064c080148190a7c3218867f1f572 |
completed | March 22, 2026, 9:53 p.m. |
Created at: March 22, 2026, 4:29 p.m.