Triple

T3696883
Position Surface form Disambiguated ID Type / Status
Subject Kot Diji E78478 entity
Predicate hasArchaeologicalStratum P31670 FINISHED
Object pre-Harappan layer 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: pre-Harappan layer | Statement: [Kot Diji, hasArchaeologicalStratum, pre-Harappan layer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasArchaeologicalStratum
Context triple: [Kot Diji, hasArchaeologicalStratum, pre-Harappan layer]
  • A. hasArchaeologicalLayer chosen
    Indicates that one entity contains, corresponds to, or is associated with a specific archaeological stratigraphic layer within it.
  • B. hasArchaeologicalFeature
    Indicates that an entity possesses, contains, or is associated with a specific archaeological feature or structure.
  • C. hasArchaeologicalMound
    Indicates that an entity possesses or contains an archaeological mound, i.e., a raised earthwork or mound of archaeological significance located on or within it.
  • D. hasArchaeologicalCulture
    Indicates that an entity is associated with, belongs to, or is characterized by a particular archaeological culture.
  • E. hasArchaeologicalSiteType
    Indicates that an entity is classified as, or associated with, a specific type or category of archaeological site.
  • 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_69ad85e3b1888190abc983e06968696d completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc5115ad8819085ffa938de3943f4 completed March 8, 2026, 6:50 p.m.
PD Predicate disambiguation batch_69adb84dc5808190850aa6975cb09e27 completed March 8, 2026, 5:56 p.m.
Created at: March 8, 2026, 3:26 p.m.