Triple
T17330950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dotaku |
E420812
|
entity |
| Predicate | typicalLocationFound |
P91034
|
FINISHED |
| Object | burial sites |
—
|
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: burial sites | Statement: [Dotaku, typicalLocationFound, burial sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLocationFound Context triple: [Dotaku, typicalLocationFound, burial sites]
-
A.
locationFound
Indicates that a particular entity is located or discovered at a specific place or position.
-
B.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
C.
typicalUseLocation
Indicates the usual or most common location where an entity is used or operates.
-
D.
oftenLocatedAt
chosen
Indicates that an entity is frequently or commonly found at, or associated with being in, a particular location.
-
E.
ashFoundIn
Indicates that ash is present within, or has been discovered in, a specified location or material.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e439d5c788819092bdc4d3de0ec958 |
completed | April 19, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:43 a.m.