Triple

T35847147
Position Surface form Disambiguated ID Type / Status
Subject Villa San Marco E1036243 entity
Predicate reexcavatedIn P38373 FINISHED
Object 20th century 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: 20th century | Statement: [Villa San Marco, reexcavatedIn, 20th century]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reexcavatedIn
Context triple: [Villa San Marco, reexcavatedIn, 20th century]
  • A. excavatedFor
    Indicates that something has been dug out or uncovered from the ground specifically for the benefit, use, or purpose of another entity.
  • B. excavatedAfter
    Indicates that one excavation event occurred later in time than another excavation event.
  • C. excavatedAs
    Indicates that one entity has been dug out, uncovered, or removed from its surrounding material or context in the form or role of another specified entity.
  • D. excavatedIn chosen
    Indicates that something (typically an artifact, structure, or site) was uncovered or dug out during an excavation that took place at a specific time or within a specific time period.
  • E. excavatedFrom
    Indicates that something (typically an artifact, fossil, or material) was dug out or uncovered from a specific location or source through excavation.
  • 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_69f76e1a29e8819088280f26096aeb55 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7aa3883d48190b05e3d2da7a017ae completed May 3, 2026, 8:04 p.m.
PD Predicate disambiguation batch_69f7a8d435288190b30b1991fb003121 completed May 3, 2026, 7:58 p.m.
Created at: May 3, 2026, 4:06 p.m.