Triple
T1840540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caroline Plate |
E41166
|
entity |
| Predicate | hasMotionType |
P23273
|
FINISHED |
| Object | generally westward relative motion |
—
|
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: generally westward relative motion | Statement: [Caroline Plate, hasMotionType, generally westward relative motion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMotionType Context triple: [Caroline Plate, hasMotionType, generally westward relative motion]
-
A.
hasMovementType
chosen
Indicates the type or mode of movement associated with an entity, such as how it moves or is transported.
-
B.
modelsMotionOf
Indicates that one entity provides a representation or simulation of the motion or movement behavior of another entity.
-
C.
hasKinematicProperty
Indicates that an entity possesses a specific motion-related characteristic, such as velocity, acceleration, or trajectory.
-
D.
hasActivityType
Indicates the specific kind or category of activity associated with an entity or event.
-
E.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.