Triple
T33240371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elessar |
E850945
|
entity |
| Predicate | bearsInscription |
P4188
|
FINISHED |
| Object | none mentioned in the published text |
—
|
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: none mentioned in the published text | Statement: [Elessar, bearsInscription, none mentioned in the published text]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearsInscription Context triple: [Elessar, bearsInscription, none mentioned in the published text]
-
A.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
-
B.
mayBeInscribedOn
Indicates that one entity is permitted or suitable to be written, engraved, or otherwise inscribed on another entity.
-
C.
inscribedOn
chosen
Indicates that text, symbols, or markings are written or carved onto the surface of an object.
-
D.
materialTypicallyInscribedOn
Indicates the material that is most commonly used as the surface or medium on which something is inscribed.
-
E.
mayBeInscribedAs
Indicates that one entity is permitted or suitable to be formally recorded, written, or engraved as another entity.
- 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:31 a.m.