Triple
T2837240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aegean Sea Plate |
E62379
|
entity |
| Predicate | deforms |
P35342
|
FINISHED |
| Object | continental crust of the Aegean region |
—
|
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: continental crust of the Aegean region | Statement: [Aegean Sea Plate, deforms, continental crust of the Aegean region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: deforms Context triple: [Aegean Sea Plate, deforms, continental crust of the Aegean region]
-
A.
deformationFeatures
chosen
Indicates the presence or characteristics of structural changes or distortions (such as folds, faults, or warps) affecting an object or material.
-
B.
deformationStyle
Indicates the manner or pattern in which an object or material is deformed under applied forces or conditions.
-
C.
shaped
Indicates that one entity has given form, contour, or structure to another entity or outcome.
-
D.
hasInternalDeformation
Indicates that one entity exhibits structural distortion or change within its interior caused by stress, force, or other internal factors.
-
E.
shape
Indicates that one entity has a particular geometric or physical form characterized by the other entity.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdeede0488190a9782f55b57559ee |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:01 p.m.