Triple
T1199035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kubla Khan |
E25735
|
entity |
| Predicate | settingDescription |
P25484
|
FINISHED |
| Object | pleasure-dome |
—
|
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: pleasure-dome | Statement: [Kubla Khan, settingDescription, pleasure-dome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingDescription Context triple: [Kubla Khan, settingDescription, pleasure-dome]
-
A.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
B.
describes
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
C.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
D.
usedAsSettingFor
Indicates that one entity serves as the backdrop, location, or environment in which another entity (such as an event, story, or activity) takes place.
-
E.
section8Description
Indicates a textual description or explanation related to Section 8, typically detailing its terms, conditions, or relevant information.
- F. None of above. chosen
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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9d56748190a12fe4a30346f1d8 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5ed2b88190aab992913957e1cf |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bcc82e38819081c3615e1cc7a66f |
completed | March 1, 2026, 10:25 p.m. |
Created at: March 1, 2026, 7:46 p.m.