Triple

T31840332
Position Surface form Disambiguated ID Type / Status
Subject Aratta E812784 entity
Predicate conflictTypeInMyths P1397 FINISHED
Object diplomatic rivalry with Uruk 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: diplomatic rivalry with Uruk | Statement: [Aratta, conflictTypeInMyths, diplomatic rivalry with Uruk]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: conflictTypeInMyths
Context triple: [Aratta, conflictTypeInMyths, diplomatic rivalry with Uruk]
  • A. conflictType chosen
    Indicates the specific kind or category of conflict that characterizes the relationship or interaction between entities.
  • B. mythologicalContent
    Indicates that the subject contains, references, or is associated with myths, mythological narratives, or myth-based elements.
  • C. mainConflict
    Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
  • D. mythologicalCategory
    Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
  • E. mythologicalConsequence
    Indicates a causal or resultant relationship where one entity brings about, embodies, or suffers a consequence within a mythological or legendary narrative context.
  • 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_69f348ea7ffc8190a2ab43d80277cf59 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f6ffbad8848190867c2988c0ceb84f completed May 3, 2026, 7:56 a.m.
PD Predicate disambiguation batch_69f6fc53f4f881908dcc698687bbb64d completed May 3, 2026, 7:42 a.m.
Created at: April 30, 2026, 11:49 p.m.