Triple

T2887799
Position Surface form Disambiguated ID Type / Status
Subject Geb E59547 entity
Predicate consort P13 FINISHED
Object Nut E56546 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: Nut | Statement: [Geb, consort, Nut]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nut
Context triple: [Geb, consort, Nut]
  • A. Nut chosen
    Nut is the ancient Egyptian sky goddess, often depicted arching over the earth and associated with the heavens, stars, and the cyclical rebirth of the sun.
  • B. Ng
    Ng is a common Chinese surname found across various Chinese-speaking communities and the diaspora, often representing the Cantonese or Hokkien romanization of the character 吳 (Wu).
  • C. nan
    nan is the ISO 639-3 language code assigned to the Teochew (Chaoshan) Chinese language variety spoken primarily in eastern Guangdong, China, and among overseas Chinese communities.
  • D. NU
    NU is a leading Japanese national research university located in Nagoya, known for its strong programs in science, engineering, and the humanities.
  • E. NU
    NU is the official two-letter Canada Post abbreviation for the northern Canadian territory of Nunavut.
  • 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_69ab4ac739188190a112f42a5a69c951 completed March 6, 2026, 9:44 p.m.
NER Named-entity recognition batch_69abe047aa7c8190a0ed570c13f3a1a2 completed March 7, 2026, 8:22 a.m.
NED1 Entity disambiguation (via context triple) batch_69b055f2d72c8190b81b2b0b3093ae57 completed March 10, 2026, 5:33 p.m.
Created at: March 6, 2026, 10:03 p.m.