Triple

T15489911
Position Surface form Disambiguated ID Type / Status
Subject Pennut E378652 entity
Predicate archaeologicalSite P1098 FINISHED
Object Aniba E378651 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: Aniba | Statement: [Pennut, archaeologicalSite, Aniba]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aniba
Context triple: [Pennut, archaeologicalSite, Aniba]
  • A. Aniba chosen
    Aniba was an ancient Nubian settlement in Lower Nubia that served as an important Egyptian administrative and military center, especially during the Middle and New Kingdoms.
  • B. Abanilla
    Abanilla is a municipality in the Region of Murcia in southeastern Spain, known for its traditional agriculture and historic religious festivities.
  • C. Mussaenda
    Mussaenda is a genus of tropical flowering shrubs and small trees known for their showy, brightly colored bracts that resemble petals.
  • D. Bansberia
    Bansberia is a historic town in West Bengal, India, known for its terracotta temples and riverside location along the Hooghly River.
  • E. Shimea
    Shimea is a biblical figure mentioned in the Hebrew Bible as one of King David’s brothers.
  • 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_69d85cd53a7c819080f5b9042c4c199e completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03fac2af88190ac1d119e6b21dbe0 completed April 16, 2026, 1:47 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff3d4661088190bb53161247effcc4 completed May 9, 2026, 1:57 p.m.
Created at: April 10, 2026, 3:48 a.m.