Triple
T8493459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abel (Abel of Sark) |
E201031
|
entity |
| Predicate | associatedWithFictionalPlace |
P21117
|
FINISHED |
| Object | planet Sark |
—
|
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: planet Sark | Statement: [Abel (Abel of Sark), associatedWithFictionalPlace, planet Sark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFictionalPlace Context triple: [Abel (Abel of Sark), associatedWithFictionalPlace, planet Sark]
-
A.
hasFictionalLocation
chosen
Indicates that an entity is associated with, set in, or takes place within a location that exists only in fiction rather than in the real world.
-
B.
basedInFictionalLocation
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
-
C.
depictsFictionalPlace
Indicates that one entity visually represents or portrays a place that exists only in fiction rather than in the real world.
-
D.
fictionalPlaceType
Indicates that a place is a fictional location and specifies what type or category of fictional place it is.
-
E.
residesInFictionalLocation
Indicates that an entity lives or is based in a location that is explicitly fictional or imaginary.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe579b7088190b297b04527e36a2b |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:13 p.m.