Triple
T31807194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Natalian Boer |
E811904
|
entity |
| Predicate | regionAssociationNature |
P197824
|
FINISHED |
| Object | fictional |
—
|
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: fictional | Statement: [Natalian Boer, regionAssociationNature, fictional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionAssociationNature Context triple: [Natalian Boer, regionAssociationNature, fictional]
-
A.
regionOfAssociation
Indicates a broader geographic or spatial area with which an entity is functionally, contextually, or organizationally associated.
-
B.
nearNaturalRegion
Indicates that one entity is located close to a specified natural region or area in geographic space.
-
C.
naturalRegionOf
Indicates that one entity is the natural geographic region or area in which the other entity is located or to which it belongs.
-
D.
naturalRegionType
Indicates the type or category of natural region to which a given area or place belongs.
-
E.
nationalOrRegionalAssociation
Indicates a relationship where an entity is formally associated with, governed by, or represented through a specific national or regional organization or body.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
| PDg | Predicate description generation | batch_69feafa0acd881908bb6c01635b5537a |
completed | May 9, 2026, 3:53 a.m. |
Created at: April 30, 2026, 11:43 p.m.