Triple

T23307970
Position Surface form Disambiguated ID Type / Status
Subject Velathri E590501 entity
Predicate hasNotableArtifactType P40733 FINISHED
Object Etruscan funerary urns 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: Etruscan funerary urns | Statement: [Velathri, hasNotableArtifactType, Etruscan funerary urns]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNotableArtifactType
Context triple: [Velathri, hasNotableArtifactType, Etruscan funerary urns]
  • A. hasNotableType
    Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
  • B. hasSignificantArtifact
    Indicates that an entity possesses or is associated with an artifact that is of notable importance, influence, or relevance within a given context.
  • C. hasNotableItem
    Indicates that an entity possesses, contains, or is associated with an item considered notable or significant in some context.
  • D. hasTypeOfArtifact chosen
    Indicates that one entity is classified as, or belongs to, a particular type or category of artifact in relation to another entity.
  • E. hasCharacteristicArtifact
    Indicates that an entity is associated with a specific artifact that characterizes, exemplifies, or is typical of it.
  • 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_69e25d1c0ecc8190a355aa229f06d0e0 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f197292fd08190bc364e1433dde213 completed April 29, 2026, 5:29 a.m.
PD Predicate disambiguation batch_69effcf325f88190b320268c3c551abb completed April 28, 2026, 12:18 a.m.
Created at: April 17, 2026, 5:05 p.m.