Triple
T30403183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andaman microplate |
E773404
|
entity |
| Predicate | relativeMotionWith |
P7348
|
FINISHED |
| Object | Indian Plate |
E237727
|
NE 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: Indian Plate | Statement: [Andaman microplate, relativeMotionWith, Indian Plate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeMotionWith Context triple: [Andaman microplate, relativeMotionWith, Indian Plate]
-
A.
relativeMotionType
chosen
Indicates the type or nature of motion occurring between two entities relative to one another.
-
B.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
C.
relativePositioning
Indicates how one entity is spatially arranged or located in relation to another entity.
-
D.
meanMotionRelation
Indicates a relationship where one entity’s mean orbital motion is defined, compared, or constrained with respect to another entity or reference frame.
-
E.
motionRelativeToEarth
Indicates movement or change in position of an entity as measured or perceived relative to the Earth as a reference frame.
- F. None of above.
Provenance (4 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a02f2d6f35481909829d4ec710dcb0f |
completed | May 12, 2026, 9:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2798adcec48190937a14053147f875 |
completed | June 9, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_6a02f15a2460819080cb4be5b50221d0 |
completed | May 12, 2026, 9:22 a.m. |
Created at: April 29, 2026, 8:03 p.m.