Triple
T29210939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puhar |
E740543
|
entity |
| Predicate | destructionTradition |
P49010
|
FINISHED |
| Object | submergence by the sea |
—
|
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: submergence by the sea | Statement: [Puhar, destructionTradition, submergence by the sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destructionTradition Context triple: [Puhar, destructionTradition, submergence by the sea]
-
A.
traditionallyDestroyedAt
Indicates that something is customarily or historically destroyed at a particular time, place, or event according to tradition.
-
B.
typeOfDestruction
chosen
Indicates the specific manner or method by which something is destroyed or caused to cease to exist.
-
C.
citesTradition
Indicates that one entity references, appeals to, or draws authority from a tradition associated with another entity.
-
D.
sufferedDestructionOf
Indicates that one entity experienced damage, ruin, or loss as a result of the destruction of another entity.
-
E.
designedToDestroy
Indicates that one entity was intentionally created or configured for the purpose of damaging, disabling, or annihilating another 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 12:11 p.m.