Triple

T14035583
Position Surface form Disambiguated ID Type / Status
Subject Monterozzi hill E337702 entity
Predicate earliestTombsDateFrom P69130 FINISHED
Object 7th century BC 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: 7th century BC | Statement: [Monterozzi hill, earliestTombsDateFrom, 7th century BC]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: earliestTombsDateFrom
Context triple: [Monterozzi hill, earliestTombsDateFrom, 7th century BC]
  • A. earliestBurials
    Indicates that the referenced burials are among the first or oldest known interments associated with a given site, group, or context.
  • B. earliestStrataDate chosen
    Indicates the earliest known or recorded date associated with a particular geological or archaeological stratum.
  • C. earliestDate
    Indicates the earliest point in time at which an associated event, state, or relationship is considered to begin or be valid.
  • D. earliestStructuresDateFrom
    Indicates that the earliest known structures associated with an entity originate or were first constructed in a specified time period or date.
  • E. earliestLongCountDateOnMonument
    Indicates the earliest recorded Long Count calendar date that appears on a given monument.
  • 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_69d81c664e48819088cbd8f433aeffe5 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de2fac71188190a586049405f1071e completed April 14, 2026, 12:14 p.m.
PD Predicate disambiguation batch_69de05ab36b48190920efb1869bdb1fe completed April 14, 2026, 9:15 a.m.
Created at: April 9, 2026, 10:20 p.m.