Triple
T17565524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Medang royal court |
E427801
|
entity |
| Predicate | hadOfficials |
P11211
|
FINISHED |
| Object | royal ministers |
—
|
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: royal ministers | Statement: [Medang royal court, hadOfficials, royal ministers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadOfficials Context triple: [Medang royal court, hadOfficials, royal ministers]
-
A.
formerOfficialIn
Indicates that an entity once held an official position or office within another entity but no longer does.
-
B.
hasOfficial
chosen
Indicates that an entity is formally associated with, represented by, or served by a designated official or office-holder.
-
C.
hadPrincipalLeader
Indicates that an entity was led or headed by a primary or chief leader.
-
D.
hadInteriorMinister
Indicates that a country or governing body had a specific person serving in the role of interior minister.
-
E.
officersAre
Indicates that certain individuals hold the role or position of officers within a specified group, organization, or context.
- 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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4592ce42c8190a54a0a328c5e8ffc |
completed | April 19, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.