Triple
T33217291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angerthas Erebor |
E850320
|
entity |
| Predicate | usedForInscriptionType |
P16929
|
FINISHED |
| Object | inscriptions |
—
|
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: inscriptions | Statement: [Angerthas Erebor, usedForInscriptionType, inscriptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForInscriptionType Context triple: [Angerthas Erebor, usedForInscriptionType, inscriptions]
-
A.
inscriptionUsedWith
Indicates that a particular inscription is employed together with, or in association with, another object, tool, or context in which it is applied or interpreted.
-
B.
mayBeInscribedAs
Indicates that one entity is permitted or suitable to be formally recorded, written, or engraved as another entity.
-
C.
issuedInscription
Indicates that an authority or source formally created and released a specific inscription or written record.
-
D.
inscriptionType
chosen
Indicates the specific kind or category of inscription associated with an entity (e.g., dedicatory, funerary, commemorative).
-
E.
inscribedFor
Indicates that something is formally written, engraved, or dedicated for a particular recipient or purpose.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1:30 a.m.