Triple
T37854021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forest of Nivrim |
E944133
|
entity |
| Predicate | realmNearby |
P61270
|
FINISHED |
| Object | Doriath |
—
|
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: Doriath | Statement: [Forest of Nivrim, realmNearby, Doriath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realmNearby Context triple: [Forest of Nivrim, realmNearby, Doriath]
-
A.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified region.
-
B.
nearbyLocation
chosen
Indicates that one location is situated close to another location in physical space.
-
C.
nearbyFrontier
Indicates that one entity is located close to a boundary or frontier region associated with another entity.
-
D.
placesWithin
Indicates that one place or area is located entirely inside the boundaries of another place or area.
-
E.
traditionalTerritoryNearby
Indicates that one entity is located close to the traditional territory associated with 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.