Triple
T14024409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ikh Khorig |
E337419
|
entity |
| Predicate | restrictionReason |
P24667
|
FINISHED |
| Object | protection of royal burials |
—
|
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: protection of royal burials | Statement: [Ikh Khorig, restrictionReason, protection of royal burials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restrictionReason Context triple: [Ikh Khorig, restrictionReason, protection of royal burials]
-
A.
restriction
Indicates a limiting condition or rule that constrains or controls what an entity can do, use, or access in relation to another entity or context.
-
B.
reasonForSuppression
Indicates the justification or cause for which something (such as information, data, or content) has been withheld, hidden, or prevented from being shown or used.
-
C.
statedReason
Indicates that one entity expresses or provides another entity as the explanation, justification, or motive for an action, event, or claim.
-
D.
regulationReason
Indicates the reason or justification for which a regulation is established, applied, or enforced in relation to an entity or activity.
-
E.
protectionReason
chosen
Indicates the justification or cause for which protection is provided or required in the relationship between entities.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fa6ca7481908976ce748a1957b1 |
completed | April 14, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.