Triple

T9418692
Position Surface form Disambiguated ID Type / Status
Subject Anzick site E227092 entity
Predicate importanceToDiscipline P592 FINISHED
Object American archaeology 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: American archaeology | Statement: [Anzick site, importanceToDiscipline, American archaeology]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: importanceToDiscipline
Context triple: [Anzick site, importanceToDiscipline, American archaeology]
  • A. strongInDiscipline
    Indicates that an entity possesses a high level of strength, skill, or proficiency in a particular discipline or field.
  • B. educationalImportance
    Indicates the degree to which something is significant, valuable, or impactful in an educational or learning context.
  • C. supportsDiscipline
    Indicates that one entity provides assistance, resources, or endorsement that helps sustain or advance a particular discipline.
  • D. disciplineDefinedAs
    Indicates that one discipline is formally characterized, described, or specified in terms of another concept, framework, or definition.
  • E. associatedWithDiscipline chosen
    Indicates that an entity has a relevant connection or involvement with a particular academic, professional, or thematic discipline.
  • 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_69ca84359e7c819091148ba4b670e436 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd68cd1e3481909abcb715e2398120 completed April 1, 2026, 6:49 p.m.
PD Predicate disambiguation batch_69cca550777c819094e1851a6127cbbc completed April 1, 2026, 4:55 a.m.
Created at: March 30, 2026, 7:48 p.m.