Triple
T25521044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rama II |
E639648
|
entity |
| Predicate | royalHouseFoundedBy |
P77474
|
FINISHED |
| Object | Rama I |
—
|
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: Rama I | Statement: [Rama II, royalHouseFoundedBy, Rama I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalHouseFoundedBy Context triple: [Rama II, royalHouseFoundedBy, Rama I]
-
A.
royalHouseFounder
chosen
Indicates that one entity is the person who founded or established the royal house or dynasty to which the other entity belongs.
-
B.
lastRoyalHouseFounded
Indicates that one entity is the most recently established royal house associated with another entity (such as a country, realm, or dynasty sequence).
-
C.
royalHouseOriginCountry
Indicates the country from which a royal house or dynasty originates.
-
D.
dynastyFoundedRuledRegion
Indicates that a particular dynasty was established and exercised ruling authority over a specified region.
-
E.
dynastyFoundedIn
Indicates that a particular dynasty was established or came into existence in a specified time or place.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f836387c8190813f5c202ff47a8c |
completed | May 2, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 3 p.m.