Triple
T1795409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamond |
E39591
|
entity |
| Predicate | transportToSurface |
P11822
|
FINISHED |
| Object | brought to surface by volcanic eruptions |
—
|
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: brought to surface by volcanic eruptions | Statement: [Diamond, transportToSurface, brought to surface by volcanic eruptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportToSurface Context triple: [Diamond, transportToSurface, brought to surface by volcanic eruptions]
-
A.
transportFor
chosen
Indicates a relationship where one entity serves as the means or service used to move another entity from one place to another.
-
B.
surfaceType
Indicates the kind or classification of surface associated with an entity or interaction.
-
C.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
-
D.
surfaceBehavior
Indicates how an entity behaves or interacts specifically at or on its surface.
-
E.
playsOnSurface
Indicates that an entity performs or engages in an activity while being in contact with or supported by a particular surface.
- 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_69a88631854081909723959921e45c2b |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.