Triple
T185539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horologium Oscillatorium |
E3971
|
entity |
| Predicate | part |
P3120
|
FINISHED |
| Object | Part I: On the center of oscillation |
—
|
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: Part I: On the center of oscillation | Statement: [Horologium Oscillatorium, part, Part I: On the center of oscillation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: part Context triple: [Horologium Oscillatorium, part, Part I: On the center of oscillation]
-
A.
section
chosen
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
B.
partOfProcess
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
-
C.
party
Indicates that an entity participates as a side or participant in an event, agreement, or situation.
-
D.
participant
Indicates that an entity takes part in, is involved in, or plays a role within a specified event, activity, or process.
-
E.
participation
Indicates that an entity takes part in, contributes to, or is involved in a shared activity, event, or process with others.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2592867108190b5d316c055575449 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566fb08c81908faff2fde552105d |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.