Triple
T33112745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruinen |
E847372
|
entity |
| Predicate | cartographicallyDepictedIn |
P58961
|
FINISHED |
| Object | Maps of Middle-earth |
—
|
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: Maps of Middle-earth | Statement: [Bruinen, cartographicallyDepictedIn, Maps of Middle-earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cartographicallyDepictedIn Context triple: [Bruinen, cartographicallyDepictedIn, Maps of Middle-earth]
-
A.
cartographyBy
Indicates that one entity is the creator or producer of the cartographic work (such as a map or chart) associated with another entity.
-
B.
cartographicWork
Indicates a relationship where one entity is a cartographic work (such as a map or chart) that represents geographic information about another entity.
-
C.
mapsDepict
chosen
Indicates that maps visually represent or illustrate the geographic features, locations, or spatial relationships of something.
-
D.
depictsCountry
Indicates that one entity visually represents or portrays a specific country.
-
E.
cartographicContent
Indicates that the resource contains or is associated with map-related or cartographic information.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6ec34a481908851cd68697cb88c |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.