Triple

T22247755
Position Surface form Disambiguated ID Type / Status
Subject Dukedom of Atholl E549888 entity
Predicate hasUniquePrivilege P3162 FINISHED
Object maintains private army 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: maintains private army | Statement: [Dukedom of Atholl, hasUniquePrivilege, maintains private army]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUniquePrivilege
Context triple: [Dukedom of Atholl, hasUniquePrivilege, maintains private army]
  • A. holderPrivileges
    Indicates that one entity possesses specific rights, permissions, or advantages granted to the holder of another entity.
  • B. requiresPrivileges
    Indicates that performing the referenced action or accessing the referenced resource is contingent on the actor having specific privileges or permissions.
  • C. entailsPrivileges chosen
    Indicates that one entity’s status, action, or condition grants or carries with it specific rights, powers, or privileges for another entity or itself.
  • D. hasRightsOver
    Indicates that one entity possesses legal, moral, or formal entitlements or authority over another entity.
  • E. hasAccessTo
    Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
  • 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_69e11e41d9408190bd770cf282e22753 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f13219dc3481908dd987c4e98623e6 completed April 28, 2026, 10:18 p.m.
PD Predicate disambiguation batch_69e72fe1e0cc8190bd13cff2a0846225 completed April 21, 2026, 8:05 a.m.
Created at: April 16, 2026, 8:38 p.m.