Triple
T11047443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sea of Rhûn |
E261168
|
entity |
| Predicate | mapFeatureIn |
P36479
|
FINISHED |
| Object | The Lord of the Rings 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: The Lord of the Rings maps | Statement: [Sea of Rhûn, mapFeatureIn, The Lord of the Rings maps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapFeatureIn Context triple: [Sea of Rhûn, mapFeatureIn, The Lord of the Rings maps]
-
A.
mapsFrom
Indicates that one entity is derived, transformed, or constructed based on data, structure, or content originating from another entity.
-
B.
mapsDepict
Indicates that maps visually represent or illustrate the geographic features, locations, or spatial relationships of something.
-
C.
mapNumber
Indicates a correspondence where each element in one set or collection is assigned a specific numeric value in another set or domain.
-
D.
mapLocation
chosen
Indicates a relationship where an entity is associated with a specific position or area on a map.
-
E.
mapDisplay
Indicates that something is being visually represented or shown on a map interface.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798315b988190bc565581b2664009 |
completed | April 9, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.