Triple

T30168944
Position Surface form Disambiguated ID Type / Status
Subject Kingdom of Ur E766865 entity
Predicate hasBureaucraticElement P178614 FINISHED
Object tax collection system 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: tax collection system | Statement: [Kingdom of Ur, hasBureaucraticElement, tax collection system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBureaucraticElement
Context triple: [Kingdom of Ur, hasBureaucraticElement, tax collection system]
  • A. hasPoliticalBureau
    Indicates that an entity possesses or is associated with a political bureau as part of its organizational or governance structure.
  • B. hasGovernmentalBodyType
    Indicates the specific kind or classification of governmental body that an entity possesses or is associated with.
  • C. hadExecutiveBranch
    Indicates that an entity possessed or was associated with a particular executive branch as part of its governmental or organizational structure.
  • D. hasAdministrativeEquivalent
    Indicates that two entities hold equivalent roles, powers, or status within an administrative or governance structure.
  • E. hasExecutiveAuthority
    Indicates that one entity holds formal decision-making and managerial power over an organization, group, or process.
  • 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_69f2247a968881909d79c18f2bfcb275 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f7117e55908190a67105e92bc4830f completed May 3, 2026, 9:12 a.m.
PD Predicate disambiguation batch_69f70f380690819090cc34763ba460ed completed May 3, 2026, 9:02 a.m.
PDg Predicate description generation batch_69f7117cf2188190b29e36fc1e342c60 completed May 3, 2026, 9:12 a.m.
Created at: April 29, 2026, 7:24 p.m.