Triple
T32189041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sacred Oaks |
E822185
|
entity |
| Predicate | knownInFictionalContext |
P98600
|
FINISHED |
| Object | Basin City setting |
—
|
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: Basin City setting | Statement: [Sacred Oaks, knownInFictionalContext, Basin City setting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownInFictionalContext Context triple: [Sacred Oaks, knownInFictionalContext, Basin City setting]
-
A.
worksInFictionalContext
Indicates that an entity performs work or fulfills a role within a fictional or imagined setting rather than in real-world circumstances.
-
B.
locatedInFictionalContext
chosen
Indicates that one entity exists or occurs within the setting or universe of a fictional work associated with another entity.
-
C.
isFictionalPersonFrom
Indicates that a fictional person originates from or is associated with a particular place or source.
-
D.
livesInFiction
Indicates that one entity exists or resides within the fictional world or narrative setting created by another entity.
-
E.
usedInFictionalWork
Indicates that something (such as a concept, object, or character) appears or is employed within a specific fictional work.
- 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_69f3490819cc81909bae1f8ce99423c5 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 12:35 a.m.