Triple
T36558063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Himling |
E901746
|
entity |
| Predicate | remnantOfRegion |
P99373
|
FINISHED |
| Object | eastern Beleriand |
—
|
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: eastern Beleriand | Statement: [Himling, remnantOfRegion, eastern Beleriand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: remnantOfRegion Context triple: [Himling, remnantOfRegion, eastern Beleriand]
-
A.
remnantRegion
chosen
Indicates that a region is a leftover or remaining part of something that previously existed or was larger.
-
B.
destroyedRegion
Indicates that an entity has caused the destruction or severe damage of a specified region.
-
C.
remnantName
Indicates that an entity is identified by a name specifically associated with a remaining part, leftover, or surviving fragment of something previously whole.
-
D.
remnantType
Indicates the specific kind or category of remnant that results from or is associated with an entity or process.
-
E.
ruledRemnantsOf
Indicates that one entity exercised governing authority or control over the remaining parts or survivors of another entity after its decline, collapse, or partial destruction.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:11 p.m.