Triple
T1007964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth lithosphere |
E21755
|
entity |
| Predicate | motionDriver |
P12894
|
FINISHED |
| Object | mantle convection |
—
|
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: mantle convection | Statement: [Earth lithosphere, motionDriver, mantle convection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motionDriver Context triple: [Earth lithosphere, motionDriver, mantle convection]
-
A.
modelsMotionOf
Indicates that one entity provides a representation or simulation of the motion or movement behavior of another entity.
-
B.
mobilityComponent
Indicates that one entity functions as a mobility-related component or module that enables or affects the movement capabilities of another entity.
-
C.
motorConfiguration
Indicates the specific arrangement, setup, or parameters defining how a motor is configured or operates within a system.
-
D.
drives
Indicates that one entity operates and controls the movement of a vehicle or similar conveyance transporting themselves or others.
-
E.
movementCause
chosen
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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7f4c66c8190b6098fb72c1465a3 |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b7203124819091de68cba5f731c1 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.