Triple

T15361767
Position Surface form Disambiguated ID Type / Status
Subject Arsites E367304 entity
Predicate rejectedProposal P86103 FINISHED
Object scorched earth strategy in Asia Minor against Alexander 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: scorched earth strategy in Asia Minor against Alexander | Statement: [Arsites, rejectedProposal, scorched earth strategy in Asia Minor against Alexander]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rejectedProposal
Context triple: [Arsites, rejectedProposal, scorched earth strategy in Asia Minor against Alexander]
  • A. rejectedConcept chosen
    Indicates that one entity has refused to accept, approve, or adopt a particular concept proposed by another entity.
  • B. rejectedBy
    Indicates that one entity has been refused, dismissed, or not accepted by another entity.
  • C. rejectedPractice
    Indicates that one party has refused to accept, endorse, or continue a particular practice, method, or behavior associated with another party.
  • D. rejectedIn
    Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
  • E. rejectedAward
    Indicates that an entity refused to accept or declined an award that was offered or granted to 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_69d85a1483788190ad93c2748e8af34b completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e03e479f188190bbbc3dcd73853e02 completed April 16, 2026, 1:41 a.m.
PD Predicate disambiguation batch_69deca991e5081908b0df3d1ee7d5338 completed April 14, 2026, 11:15 p.m.
Created at: April 10, 2026, 3:18 a.m.