Triple
T15409973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Seir |
E368559
|
entity |
| Predicate | hasEthnonym |
P1435
|
FINISHED |
| Object | Seirite |
E1109482
|
NE 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: Seirite | Statement: [Mount Seir, hasEthnonym, Seirite]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Seirite Context triple: [Mount Seir, hasEthnonym, Seirite]
-
A.
Seira
Seira is one of the islands in Indonesia’s remote Tanimbar archipelago in the Maluku province.
-
B.
Seir
chosen
Seir is a mountainous region in Edom, traditionally associated with the Horites and later the descendants of Esau in the Hebrew Bible.
-
C.
Sairan
Sairan is a metro station on the Almaty Metro system in Almaty, Kazakhstan.
-
D.
Seirah
Seirah is a biblical location mentioned in the Hebrew Bible as a place of refuge associated with the judge Ehud.
-
E.
Sooretama
Sooretama is a municipality in the Brazilian state of Espírito Santo, known for its proximity to the Sooretama Biological Reserve and its Atlantic Forest conservation areas.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ea4f13c819085d26fd32b5dca6f |
completed | April 16, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff135d65988190b35392bdf1e45985 |
completed | May 9, 2026, 10:58 a.m. |
Created at: April 10, 2026, 3:20 a.m.