Triple

T24030114
Position Surface form Disambiguated ID Type / Status
Subject Princess Atsuko Ikeda E595076 entity
Predicate becameCommonerOn P154576 FINISHED
Object marriage 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: marriage | Statement: [Princess Atsuko Ikeda, becameCommonerOn, marriage]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: becameCommonerOn
Context triple: [Princess Atsuko Ikeda, becameCommonerOn, marriage]
  • A. commonerClass
    Indicates that an entity belongs to the social or economic class of commoners, as opposed to nobility or other privileged groups.
  • B. wasConvertedToCityBy
    Indicates that an entity (typically a settlement or area) was transformed into a city through the actions or decision of another agent or authority.
  • C. commonlyAscendedFrom
    Indicates that one entity is typically or frequently derived, evolved, or originated from another entity in a common or usual lineage or source relationship.
  • D. hadSocialStratumBelow
    Indicates that one entity occupied a lower social stratum or class relative to another entity.
  • E. becamePublic
    Indicates that an entity transitioned from private or restricted status to being publicly accessible or publicly traded.
  • 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_69e288bf45f08190a1b6ed8cd0b9e86b completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1d76fbedc8190a2f936729cb69993 completed April 29, 2026, 10:03 a.m.
PD Predicate disambiguation batch_69f1764345388190a3102b62ddb729b4 completed April 29, 2026, 3:08 a.m.
PDg Predicate description generation batch_69f1785afe3c81909be28986ffe944bf completed April 29, 2026, 3:17 a.m.
Created at: April 17, 2026, 9:55 p.m.