Triple
T25466561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Sirivannavari Nariratana |
E638189
|
entity |
| Predicate | isRoyaltyOf |
P44258
|
FINISHED |
| Object | Kingdom of Thailand |
—
|
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: Kingdom of Thailand | Statement: [Princess Sirivannavari Nariratana, isRoyaltyOf, Kingdom of Thailand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRoyaltyOf Context triple: [Princess Sirivannavari Nariratana, isRoyaltyOf, Kingdom of Thailand]
-
A.
associatedWithRoyalty
Indicates a relationship in which an entity has a notable connection to royalty, such as through lineage, service, patronage, or symbolic affiliation.
-
B.
hasRoyalConnection
Indicates a relationship where an entity is linked or associated in some notable way to royalty, a royal family, or a royal institution.
-
C.
hasRoyalAncestryFrom
Indicates that one entity possesses royal lineage or descent originating from another entity.
-
D.
hasRoyalStatus
chosen
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
-
E.
hasRoyalCircle
Indicates that an entity belongs to, is part of, or is associated with a royal or monarch’s inner circle or court.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f74e449c8190afaa3c05496ed598 |
completed | May 2, 2026, 1:08 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:15 p.m.