Triple
T16377584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ode Marítima |
E397714
|
entity |
| Predicate | imaginedSetting |
P18263
|
FINISHED |
| Object | high seas |
—
|
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: high seas | Statement: [Ode Marítima, imaginedSetting, high seas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imaginedSetting Context triple: [Ode Marítima, imaginedSetting, high seas]
-
A.
basedInFictionalSetting
Indicates that an entity’s primary location or setting exists within a fictional or imaginary world rather than the real world.
-
B.
settingOfFictionalResidence
Indicates that a location serves as the setting or backdrop for a fictional residence within a narrative work.
-
C.
fictionalCitySetting
Indicates that a narrative, event, or work is set in a city that is imaginary or does not exist in the real world.
-
D.
setInFictionalLocation
chosen
Indicates that an event, story, or narrative takes place within a fictional or imagined location rather than a real-world setting.
-
E.
basedInFictionalLocation
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319d8a40c8190af37e7ed60b9c4dd |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:08 a.m.