Triple
T28974580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhûn |
E734372
|
entity |
| Predicate | mapAppearance |
P57784
|
FINISHED |
| Object | eastern edge of most Middle-earth maps |
—
|
LITERAL FINISHED |
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 edge of most Middle-earth maps | Statement: [Rhûn, mapAppearance, eastern edge of most Middle-earth maps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapAppearance Context triple: [Rhûn, mapAppearance, eastern edge of most Middle-earth maps]
-
A.
mapDisplay
chosen
Indicates that something is being visually represented or shown on a map interface.
-
B.
mapVisibility
Indicates that one entity controls or reflects whether another entity is visible or hidden on a map.
-
C.
mapTheme
Indicates a thematic relationship where a map is associated with, organized by, or visually represents a particular theme or subject.
-
D.
mapUse
Indicates a relationship where one entity uses, applies, or employs a map (or mapping) to perform an action or achieve a purpose.
-
E.
mapsType
Indicates that one entity serves as a mapping whose values or outputs are of the specified type.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65ee051608190a5b73d0635d8e9c6 |
completed | May 2, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:07 a.m.