Triple

T25371294
Position Surface form Disambiguated ID Type / Status
Subject Franco-Siamese War of 1893 E632936 entity
Predicate monarchOfSiamDuringConflict P148040 FINISHED
Object Chulalongkorn NE NERFINISHED

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: Chulalongkorn | Statement: [Franco-Siamese War of 1893, monarchOfSiamDuringConflict, Chulalongkorn]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: monarchOfSiamDuringConflict
Context triple: [Franco-Siamese War of 1893, monarchOfSiamDuringConflict, Chulalongkorn]
  • A. monarchDuringWar chosen
    Indicates that a person held the position of monarch during the time span of a specified war.
  • B. monarchDuringBattle
    Indicates that one entity is the reigning monarch at the time when the other entity (a specific battle) takes place.
  • C. sultanDuringConflict
    Indicates that an individual holds the position or role of sultan during a specific conflict or period of armed struggle.
  • D. opponentMonarch
    Indicates that one monarch stands in an opposing or adversarial position to another monarch, typically in conflict or competition.
  • E. opposingMonarch
    Indicates that two monarchs are in opposition to each other, typically as rivals, enemies, or leaders of conflicting factions or states.
  • 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_69e75a90c0dc819092f928b6ea0ecc72 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f4a11323e08190a8ec4687f8fefe7f completed May 1, 2026, 12:48 p.m.
PD Predicate disambiguation batch_69f4683b34748190818428489a226124 completed May 1, 2026, 8:45 a.m.
Created at: April 21, 2026, 1:38 p.m.