Triple
T19421115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eise Eisinga Planetarium |
E485854
|
entity |
| Predicate | movementTransmission |
P113782
|
FINISHED |
| Object | wooden gears |
—
|
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: wooden gears | Statement: [Eise Eisinga Planetarium, movementTransmission, wooden gears]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementTransmission Context triple: [Eise Eisinga Planetarium, movementTransmission, wooden gears]
-
A.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
B.
movementTransition
Indicates a change in an entity’s state of motion, such as starting, stopping, or altering the direction or mode of movement.
-
C.
movementCharacteristic
Indicates how an entity moves or behaves in motion, such as its style, pattern, or quality of movement.
-
D.
movementProduction
chosen
Indicates a relationship where an entity generates, initiates, or causes physical movement or motion.
-
E.
movementCause
Indicates that one entity’s action or event is the cause of another entity’s movement or change in location.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63214d768819082129100d7116521 |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.