Triple

T13603074
Position Surface form Disambiguated ID Type / Status
Subject Instinct E324990 entity
Predicate hasAnthropologyElement P21032 FINISHED
Object true 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: true | Statement: [Instinct, hasAnthropologyElement, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAnthropologyElement
Context triple: [Instinct, hasAnthropologyElement, true]
  • A. hasEthnographicStatus
    Indicates that an entity is associated with a particular ethnographic classification, status, or role within a cultural or social context.
  • B. hasEthnographicSource
    Indicates that there exists an ethnographic source (such as a study, report, or fieldwork documentation) that provides evidence or contextual information for the subject entity.
  • C. CulturalAnthropologyAccess
    Indicates access to or availability of cultural anthropology resources, information, or services for an entity.
  • D. hasArchaeologicalMaterial
    Indicates that an entity possesses, contains, or is associated with specific archaeological materials or artifacts.
  • E. anthropologicalSignificance chosen
    Indicates that something holds importance or value for understanding human cultures, societies, or behaviors from an anthropological perspective.
  • 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_69d80769eaf081909d82f44e484d6113 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbbb9ee3f081909056dc1a92c40b7a completed April 12, 2026, 3:34 p.m.
PD Predicate disambiguation batch_69dbae1b3ee481909bd43ded6227a3e5 completed April 12, 2026, 2:37 p.m.
Created at: April 9, 2026, 9:49 p.m.