Triple
T14024406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ikh Khorig |
E337419
|
entity |
| Predicate | believedToContain |
P112524
|
FINISHED |
| Object | royal tombs |
—
|
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 tombs | Statement: [Ikh Khorig, believedToContain, royal tombs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: believedToContain Context triple: [Ikh Khorig, believedToContain, royal tombs]
-
A.
typicallyContain
Indicates that one entity is normally or commonly found within, included in, or held by another entity under usual circumstances.
-
B.
believedTo
Indicates that one entity holds a belief or conviction about the truth, existence, or properties of another entity or proposition.
-
C.
containedWith
Indicates that one entity is located or kept inside the bounds or interior space of another entity.
-
D.
believedToBelongTo
Indicates that something is thought or assumed, but not definitively known, to be owned by or part of a particular entity.
-
E.
alsoContains
Indicates that something includes, in addition to its primary contents, another specified element or component.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:19 p.m.