Triple
T21086486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tambora people |
E519501
|
entity |
| Predicate | cultureStatus |
P142777
|
FINISHED |
| Object | largely lost |
—
|
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: largely lost | Statement: [Tambora people, cultureStatus, largely lost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cultureStatus Context triple: [Tambora people, cultureStatus, largely lost]
-
A.
popularCultureStatus
Indicates the degree to which something is recognized, influential, or prominent within mainstream popular culture.
-
B.
cultStatus
Indicates that something has achieved a devoted, niche following or admiration that is disproportionate to its mainstream popularity.
-
C.
cultureCondition
Indicates the specific environmental or experimental conditions under which a biological or cell culture is maintained or grown.
-
D.
cultureHeroIn
Indicates that an entity serves as a culture hero within a specified cultural or mythological tradition.
-
E.
countryOfCult
Indicates that a particular cult, religious group, or worship practice is associated with, originates from, or is primarily practiced in a specific country.
- 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094ad1c08190a4b9d2668a6362b2 |
completed | April 21, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2e03d88819086f8b641656ad8b0 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:50 p.m.