Triple
T550100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Explorer Plate |
E11818
|
entity |
| Predicate | relativeMotion |
P7365
|
FINISHED |
| Object | moving northeast relative to Pacific Plate |
—
|
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: moving northeast relative to Pacific Plate | Statement: [Explorer Plate, relativeMotion, moving northeast relative to Pacific Plate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeMotion Context triple: [Explorer Plate, relativeMotion, moving northeast relative to Pacific Plate]
-
A.
relativeMotionType
Indicates the type or nature of motion occurring between two entities relative to one another.
-
B.
properMotion
Indicates the apparent angular movement of an astronomical object across the sky relative to distant background objects over time.
-
C.
movesRelativeTo
chosen
Indicates that one entity changes its position or orientation with respect to another entity, rather than with respect to a fixed reference frame.
-
D.
velocityRelativeToSun
Indicates the speed and direction of an entity’s motion measured with respect to the Sun as the reference frame.
-
E.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49901e4e481909a5ed93c21ab37bd |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494bae210819093c2e0d33a8ca51a |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.