Triple

T3579434
Position Surface form Disambiguated ID Type / Status
Subject Philip III Arrhidaeus E75763 entity
Predicate realPowerHeldBy P33745 FINISHED
Object regents 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: regents | Statement: [Philip III Arrhidaeus, realPowerHeldBy, regents]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: realPowerHeldBy
Context triple: [Philip III Arrhidaeus, realPowerHeldBy, regents]
  • A. realPower chosen
    Indicates that an entity possesses genuine, effective control or influence over another entity or situation, beyond nominal or formal authority.
  • B. heldTemporalPower
    Indicates that an entity exercised governing or authoritative control over another entity or domain during a specific period of time.
  • C. powerBy
    Indicates that one entity operates, functions, or is made possible through the energy, resources, or enabling capabilities provided by another entity.
  • D. exclusivePower
    Indicates that one entity holds sole authority or control over another entity or a specific domain, excluding others from sharing that power.
  • E. hasPower
    Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
  • 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_69ad85d5e3008190bdfe0bacdd1f5a1b completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc0ffecdc8190bf01c8ba90e3733e completed March 8, 2026, 6:33 p.m.
PD Predicate disambiguation batch_69adb83810c481909c645c08b978edc1 completed March 8, 2026, 5:56 p.m.
Created at: March 8, 2026, 3:21 p.m.