Triple
T33217295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angerthas Erebor |
E850320
|
entity |
| Predicate | appearsOnObject |
P94492
|
FINISHED |
| Object | Thror's Map |
—
|
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: Thror's Map | Statement: [Angerthas Erebor, appearsOnObject, Thror's Map]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsOnObject Context triple: [Angerthas Erebor, appearsOnObject, Thror's Map]
-
A.
mayAppearOn
chosen
Indicates that one entity is allowed or able to be shown, featured, or present on another entity (such as a platform, medium, or surface).
-
B.
appearsAs
Indicates that one entity is presented, perceived, or manifested in the form, role, or guise of another entity.
-
C.
appearsAtPosition
Indicates that an entity occurs or is located at a specific position within an ordered structure or sequence.
-
D.
presentsObject
Indicates that one entity formally introduces, displays, or offers another entity as an object (such as an item, work, or subject) to an audience or recipient.
-
E.
apparentIn
Indicates that something is visibly present, manifested, or evident within or through another thing or context.
- 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_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 1, 2026, 1:30 a.m.