Triple
T12671364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arconia apartment building |
E302688
|
entity |
| Predicate | inhabitedByInFiction |
P6481
|
FINISHED |
| Object | wealthy residents |
—
|
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: wealthy residents | Statement: [Arconia apartment building, inhabitedByInFiction, wealthy residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inhabitedByInFiction Context triple: [Arconia apartment building, inhabitedByInFiction, wealthy residents]
-
A.
hasFictionalInhabitants
Indicates that a place or setting is inhabited by fictional or imaginary beings.
-
B.
residesInFictionalLocation
Indicates that an entity lives or is based in a location that is explicitly fictional or imaginary.
-
C.
basedInFictionalSetting
Indicates that an entity’s primary location or setting exists within a fictional or imaginary world rather than the real world.
-
D.
inhabitedBy
chosen
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
E.
hasBranchInFictionalLocation
Indicates that an organization maintains a branch, office, or presence within a fictional or imaginary 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_69d7bdee64a08190801c6d470aefd723 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:20 p.m.