Triple
T30599637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Running |
E778870
|
entity |
| Predicate | mapAppearsIn |
P795
|
FINISHED |
| Object | maps of Wilderland |
—
|
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: maps of Wilderland | Statement: [River Running, mapAppearsIn, maps of Wilderland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mapAppearsIn Context triple: [River Running, mapAppearsIn, maps of Wilderland]
-
A.
mapsIn
Indicates that one entity is contained or represented within another entity as part of a mapping or map-like relationship.
-
B.
mapsIncluded
Indicates that one map or mapping is contained within, or is a subset of, another map or mapping.
-
C.
appearsIn
chosen
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
D.
mapsDepict
Indicates that maps visually represent or illustrate the geographic features, locations, or spatial relationships of something.
-
E.
mapsAs
Indicates that one entity serves as a mapping or correspondence to another, typically translating or associating elements from one domain or representation to another.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689b0dbe08190aeacfb2d5386b46d |
completed | May 2, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:25 p.m.