Triple
T18802836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Pinatubo |
E459798
|
entity |
| Predicate | previously |
P122422
|
FINISHED |
| Object | volcanic crater |
—
|
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: volcanic crater | Statement: [Lake Pinatubo, previously, volcanic crater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previously Context triple: [Lake Pinatubo, previously, volcanic crater]
-
A.
previouslyIn
chosen
Indicates that an entity was located in, part of, or associated with another entity at some earlier time, but is not necessarily so now.
-
B.
previouslyBasedOn
Indicates that something was formerly derived from, adapted from, or dependent on another source, but is no longer based on it in its current state.
-
C.
previouslyObserved
Indicates that the subject entity has been seen, recorded, or encountered at some earlier time prior to the current context.
-
D.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
E.
previouslyEstablished
Indicates that the relationship or condition it connects has already been formed or confirmed at an earlier time before the current context.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a0253f748190998995e3b1524357 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.