Triple
T26255170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stern–Brocot tree |
E656695
|
entity |
| Predicate | originalMotivation |
P189741
|
FINISHED |
| Object | optimization of gear ratios |
—
|
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: optimization of gear ratios | Statement: [Stern–Brocot tree, originalMotivation, optimization of gear ratios]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalMotivation Context triple: [Stern–Brocot tree, originalMotivation, optimization of gear ratios]
-
A.
initialMotivation
chosen
Indicates the original reason, drive, or purpose that prompts an entity to begin an action, behavior, or process.
-
B.
originalReason
Indicates the initial cause, motivation, or justification behind an action, decision, or state of affairs.
-
C.
motivationFor
Indicates that one entity serves as the reason, drive, or incentive behind another entity’s action, state, or occurrence.
-
D.
laterMotivation
Indicates that one event, state, or action serves as a motivation or reason for another event, state, or action that occurs later in time.
-
E.
motivated
Indicates that one entity provides a reason, drive, or incentive that causes another entity to act or behave in a certain way.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 26, 2026, 9:08 p.m.