Triple
T26896829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arendellian |
E677918
|
entity |
| Predicate | spokenInFictionalLocation |
P161980
|
FINISHED |
| Object | Arendelle |
—
|
NE NERFINISHED |
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: Arendelle | Statement: [Arendellian, spokenInFictionalLocation, Arendelle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokenInFictionalLocation Context triple: [Arendellian, spokenInFictionalLocation, Arendelle]
-
A.
hasBranchInFictionalLocation
Indicates that an organization maintains a branch, office, or presence within a fictional or imaginary location.
-
B.
basedInFictionalLocation
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
-
C.
basedInFictionalWorkLocation
Indicates that an entity’s location or setting is situated within a fictional place as depicted in a specific creative work.
-
D.
residesInFictionalLocation
Indicates that an entity lives or is based in a location that is explicitly fictional or imaginary.
-
E.
locatedInFictionalContext
Indicates that one entity exists or occurs within the setting or universe of a fictional work associated with another entity.
- 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_69eee9befee48190a26f214faa867be7 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f62081136c81909de8090b1d6c1ac5 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fd5442081908ca677a9c81dcb3f |
completed | May 2, 2026, 4:01 p.m. |
Created at: April 27, 2026, 5:48 a.m.