Triple
T17368946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aira Caldera |
E422258
|
entity |
| Predicate | producedDeposit |
P490
|
FINISHED |
| Object | Aira-Tn tephra |
—
|
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: Aira-Tn tephra | Statement: [Aira Caldera, producedDeposit, Aira-Tn tephra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producedDeposit Context triple: [Aira Caldera, producedDeposit, Aira-Tn tephra]
-
A.
deposited
Indicates that an entity has placed or put something into another entity, typically transferring it into a container, location, or account.
-
B.
hasDeposits
Indicates that an entity holds or maintains deposited funds or resources in another entity, such as an account or institution.
-
C.
depositedOn
Indicates that one entity has placed or stored something onto or into another entity, typically as part of a deposit or accumulation process.
-
D.
deposes
Indicates the action by which one party forcibly removes another from a position of power or authority.
-
E.
produces
chosen
Indicates that one entity creates, generates, or yields another entity as a result or output.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6790448190a24047523a019f81 |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.