Triple
T600125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenape |
E11473
|
entity |
| Predicate | traditionalLanguage |
P6149
|
FINISHED |
| Object | Unami |
E75801
|
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: Unami | Statement: [Lenape, traditionalLanguage, Unami]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Unami Context triple: [Lenape, traditionalLanguage, Unami]
-
A.
Unami
chosen
Unami is a dialect of the Lenape (Delaware) language historically spoken by the Lenape people in parts of the mid-Atlantic region of North America.
-
B.
Izumiotsu
Izumiotsu is a coastal city in Osaka Prefecture, Japan, known for its port facilities and industrial waterfront along Osaka Bay.
-
C.
Kitchawan
Kitchawan is a small hamlet within the town of Yorktown in Westchester County, New York, known for its residential character and proximity to natural areas.
-
D.
Shimamoto
Shimamoto is a town in Osaka Prefecture, Japan, located between Kyoto and Osaka along the Yodo River.
-
E.
Runashimi
Runashimi is the Indigenous Kichwa (Quechua) language spoken primarily in the Andean regions of South America.
- 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_69a4932779b881908688590d59c71900 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49d78c0f08190b83ad89062ccb0b9 |
completed | March 1, 2026, 8:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a55a734f6c8190a141dafc03dd2e77 |
completed | March 2, 2026, 9:37 a.m. |
Created at: March 1, 2026, 7:35 p.m.