Triple
T33654004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MONIAC hydraulic computer |
E862172
|
entity |
| Predicate | computingPrinciple |
P152870
|
FINISHED |
| Object | hydraulic analogy |
—
|
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: hydraulic analogy | Statement: [MONIAC hydraulic computer, computingPrinciple, hydraulic analogy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: computingPrinciple Context triple: [MONIAC hydraulic computer, computingPrinciple, hydraulic analogy]
-
A.
computes
Indicates that one entity performs a calculation or processing operation to produce a result from given data or inputs.
-
B.
componentPrinciple
chosen
Indicates that one entity serves as a fundamental component or underlying principle that structurally or conceptually supports or governs another entity.
-
C.
computingModel
Indicates the computational framework, paradigm, or formal system used to perform or describe a computation.
-
D.
programmingConcept
Indicates a relationship where something is classified as or associated with a specific concept used in programming or software development.
-
E.
principleClarified
Indicates that a principle has been made clearer or more explicit, typically by explanation, refinement, or elaboration.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:42 a.m.