Triple
T7330905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cottrell atmosphere |
E168995
|
entity |
| Predicate | formsAround |
P75369
|
FINISHED |
| Object | dislocation |
—
|
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: dislocation | Statement: [Cottrell atmosphere, formsAround, dislocation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsAround Context triple: [Cottrell atmosphere, formsAround, dislocation]
-
A.
around
Indicates that one entity is located or moves on all or most sides of another entity, encircling or surrounding it spatially.
-
B.
surrounds
Indicates that one entity is located all around another entity, enclosing or encircling it on multiple sides or completely.
-
C.
organizedAround
Indicates that something is structured, arranged, or centered with respect to a particular focus, principle, or organizing element.
-
D.
formsLoopAround
Indicates that one entity extends or curves so as to create a closed loop encircling or surrounding another entity or region.
-
E.
createdAround
Indicates that something was brought into existence or produced approximately at a particular time or within an imprecise time period.
- F. None of above. chosen
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_69c68a568a6481908f11e20db7bc8446 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f0ab0b1881909f8f086b81fdddb7 |
completed | March 27, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69c6e77230048190b2c29ca6b3a65b8e |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6e80ae5688190ac3d6c1bdf9532f0 |
completed | March 27, 2026, 8:26 p.m. |
Created at: March 27, 2026, 3:03 p.m.