Triple
T27501888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galavant (TV series) score |
E694174
|
entity |
| Predicate | settingReflected |
P1957
|
FINISHED |
| Object | medieval fantasy world |
—
|
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: medieval fantasy world | Statement: [Galavant (TV series) score, settingReflected, medieval fantasy world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingReflected Context triple: [Galavant (TV series) score, settingReflected, medieval fantasy world]
-
A.
settingAfter
Indicates that one setting or configuration occurs or is applied after another in a sequence or order.
-
B.
settingEvoked
Indicates that a particular setting or environment brings about, suggests, or calls to mind a specific response, mood, or association.
-
C.
setting
chosen
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
D.
settingControlled
Indicates that one entity regulates, adjusts, or determines the configuration or parameters of another entity.
-
E.
settingChange
Indicates a change made to a configuration, environment, or parameter value from one state 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 1:11 p.m.