Triple
T35293153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloudrest |
E1019284
|
entity |
| Predicate | locationInLore |
P187938
|
FINISHED |
| Object | Summerset |
E308892
|
NE 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: Summerset | Statement: [Cloudrest, locationInLore, Summerset]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInLore Context triple: [Cloudrest, locationInLore, Summerset]
-
A.
loreLocation
chosen
Indicates that something is the place or setting where related background story, history, or world-building information is situated or associated.
-
B.
locationOfPassage
Indicates the place or area through which a passage, route, or transit occurs or is situated.
-
C.
protagonistLocation
Indicates the location or setting where the story’s main protagonist is situated at a given time.
-
D.
locatedNearFiction
Indicates that one fictional entity or place is situated close to another within an imagined or narrative context.
-
E.
narrativeLocationType
Indicates the type or role of a location within the structure or context of a narrative (e.g., setting, origin, destination).
- F. None of above.
Provenance (4 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3d177a6dcc819083216cc065f47155 |
completed | June 25, 2026, 11:56 a.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.