Triple
T37142923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helevorn |
E920163
|
entity |
| Predicate | cartographicRegion |
P25535
|
FINISHED |
| Object | East 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: East Beleriand | Statement: [Helevorn, cartographicRegion, East Beleriand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cartographicRegion Context triple: [Helevorn, cartographicRegion, East Beleriand]
-
A.
mapRegion
Indicates a relationship where a map or mapping system corresponds to, covers, or is associated with a specific geographic or logical region.
-
B.
arealRegion
chosen
Indicates that something occupies or pertains to a specific two-dimensional geographic or spatial area.
-
C.
nauticalChartRegion
Indicates that a region is covered or represented by a specific nautical chart used for marine navigation.
-
D.
cartographicContent
Indicates that the resource contains or is associated with map-related or cartographic information.
-
E.
cartographicContext
Indicates the mapping or geographic framework within which something is spatially represented or interpreted.
- 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.