Triple

T21706690
Position Surface form Disambiguated ID Type / Status
Subject ḥḏt E535787 entity
Predicate hasDeterminative P77162 FINISHED
Object crown determinative LITERAL 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: crown determinative | Statement: [ḥḏt, hasDeterminative, crown determinative]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDeterminative
Context triple: [ḥḏt, hasDeterminative, crown determinative]
  • A. hasDeterminant chosen
    Indicates that one entity functions as a determiner (e.g., article, demonstrative, quantifier) specifying or limiting the reference of another entity, typically a noun or noun phrase.
  • B. determinativeFor
    Indicates that one entity serves to uniquely identify, specify, or determine the status, interpretation, or outcome of another entity.
  • C. determinedBy
    Indicates that one entity’s state, value, or outcome is decided, controlled, or fully specified by another entity.
  • D. isDeterministic
    Indicates that the outcome of a process or function is fully determined by its inputs, with no randomness or variation between executions.
  • E. canDetermine
    Indicates that one entity has the ability or authority to find out, establish, or decide the state, value, or outcome of another entity or situation.
  • F. None of above.

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_69e0c46b44c0819088ab883ebd44e0e8 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69efb530779c819080204c3bd2f6afa2 completed April 27, 2026, 7:12 p.m.
PD Predicate disambiguation batch_69e6969113cc8190ab69855ef5667e4b completed April 20, 2026, 9:11 p.m.
Created at: April 16, 2026, 6:46 p.m.