Triple
T30633188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celebrimbor |
E779763
|
entity |
| Predicate | inscribed |
P7653
|
FINISHED |
| Object | Doors of Durin |
—
|
NE NERFINISHED |
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: Doors of Durin | Statement: [Celebrimbor, inscribed, Doors of Durin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscribed Context triple: [Celebrimbor, inscribed, Doors of Durin]
-
A.
inscribedFor
Indicates that something is formally written, engraved, or dedicated for a particular recipient or purpose.
-
B.
inscribedBy
chosen
Indicates that one object has another object written, carved, or engraved onto its surface.
-
C.
inscribedTogetherWith
Indicates that one entity is inscribed jointly with another on the same surface, object, or document as part of a single inscription context.
-
D.
inscribedAt
Indicates that an entity is formally recorded, registered, or written onto a specific object, surface, or official list at a particular place or institution.
-
E.
inscribedUnder
Indicates that one entity is written, carved, or engraved beneath another entity, typically as a subordinate or accompanying inscription.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a1ee6348190a316b92bccd14826 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:28 p.m.