Triple

T14466725
Position Surface form Disambiguated ID Type / Status
Subject Goodman Point Unit E358729 entity
Predicate hasArchaeologicalStyle P27600 FINISHED
Object Puebloan 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: Puebloan | Statement: [Goodman Point Unit, hasArchaeologicalStyle, Puebloan]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasArchaeologicalStyle
Context triple: [Goodman Point Unit, hasArchaeologicalStyle, Puebloan]
  • A. hasArchaeologicalCulture chosen
    Indicates that an entity is associated with, belongs to, or is characterized by a particular archaeological culture.
  • B. hasArchaeologicalFeature
    Indicates that an entity possesses, contains, or is associated with a specific archaeological feature or structure.
  • C. hasArchaeologicalSiteType
    Indicates that an entity is classified as, or associated with, a specific type or category of archaeological site.
  • D. hasArchaeologicalLayer
    Indicates that one entity contains, corresponds to, or is associated with a specific archaeological stratigraphic layer within it.
  • E. hasArchaeologicalValue
    Indicates that something possesses significance or worth in the study, preservation, or interpretation of past human activity through material remains.
  • 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_69d827966698819082e140837737501d completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de91f6d4c08190a12e9a5901ee3508 completed April 14, 2026, 7:13 p.m.
PD Predicate disambiguation batch_69de5c42bd3c81909a62acf30cc24d1e completed April 14, 2026, 3:24 p.m.
Created at: April 10, 2026, 1:19 a.m.