Triple
T8917215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nabu |
E212321
|
entity |
| Predicate | nameVariant |
P744
|
FINISHED |
| Object | Nebo |
E384311
|
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: Nebo | Statement: [Nabu, nameVariant, Nebo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nebo Context triple: [Nabu, nameVariant, Nebo]
-
A.
Nebo
chosen
Nebo is an ancient city located in the biblical region of Moab, often associated with nearby Mount Nebo east of the Jordan River.
-
B.
Avar Koysu
Avar Koysu is a mountain river in Dagestan, Russia, that forms one of the main headwaters of the Sulak River as it flows through the Caucasus.
-
C.
Urana
Urana is a small rural town in the Riverina region of New South Wales, Australia, known for its agricultural surroundings and historic country character.
-
D.
Nebe
Nebe is a German surname most notably associated with Arthur Nebe, a high-ranking Nazi official and SS officer during World War II.
-
E.
Οὐρανός
Οὐρανός is the ancient Greek personification of the sky and heavens, a primordial deity who fathered many of the first gods.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6610cd48819090a184c5f9465626 |
completed | April 1, 2026, 12:25 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfba4567a88190855b964bc6e3ac6f |
completed | April 3, 2026, 1:01 p.m. |
Created at: March 30, 2026, 6:56 p.m.