Triple

T3482152
Position Surface form Disambiguated ID Type / Status
Subject Parthenon sculptures E73515 entity
Predicate significantDispute P49033 FINISHED
Object ownership and repatriation debate 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: ownership and repatriation debate | Statement: [Parthenon sculptures, significantDispute, ownership and repatriation debate]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: significantDispute
Context triple: [Parthenon sculptures, significantDispute, ownership and repatriation debate]
  • A. disputeInvolves
    Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
  • B. statusDisputedBy
    Indicates that the validity, accuracy, or recognition of a status is being challenged or contested by a specified party.
  • C. disputeOrigin
    Indicates that there is disagreement or uncertainty about the source, cause, or initial point of something.
  • D. hasDisputedStatus
    Indicates that the status or classification of something is contested, uncertain, or not universally agreed upon.
  • E. hasDisputedStatusWith
    Indicates that there is a contested or unresolved status, claim, or standing between the related entities.
  • F. None of above. chosen

Provenance (4 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_69ad85b3c9b08190857cae74c7f36da9 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adbb76b5188190bf8f8a3f646a7184 completed March 8, 2026, 6:09 p.m.
PD Predicate disambiguation batch_69adae0935ac8190bfa8a8bd3dcd3301 completed March 8, 2026, 5:12 p.m.
PDg Predicate description generation batch_69adb1ecb02881908394f197e31431b4 completed March 8, 2026, 5:29 p.m.
Created at: March 8, 2026, 3:17 p.m.