Triple
T15476054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Safety Harbor archaeological culture |
E376783
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | Uzita |
E1159337
|
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: Uzita | Statement: [Safety Harbor archaeological culture, associatedWith, Uzita]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Uzita Context triple: [Safety Harbor archaeological culture, associatedWith, Uzita]
-
A.
Uzita
chosen
Uzita was a Native American chiefdom or village in present-day Florida that played a notable role in early Spanish exploration of the region.
-
B.
Uzda
Uzda is a small town in present-day Belarus, historically home to a significant Jewish community.
-
C.
Uzynagash
Uzynagash is a rural settlement in southeastern Kazakhstan that serves as a local center within the Almaty Region.
-
D.
Uz
Uz is a minor biblical figure mentioned in the Book of Genesis as one of the early descendants in Abraham’s extended family line.
-
E.
Ushba
Ushba is a striking double-summited peak in the Caucasus Mountains of Georgia, renowned among climbers for its technical difficulty and dramatic, spire-like profile.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f88a5dc8190a2d7830748e29180 |
completed | April 16, 2026, 1:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff36595bfc8190a0d60b3cb875ccc5 |
completed | May 9, 2026, 1:27 p.m. |
Created at: April 10, 2026, 3:34 a.m.