Triple
T24800820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōyashima |
E620516
|
entity |
| Predicate | mythicGeographyType |
P79050
|
FINISHED |
| Object | archipelago |
—
|
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: archipelago | Statement: [Ōyashima, mythicGeographyType, archipelago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mythicGeographyType Context triple: [Ōyashima, mythicGeographyType, archipelago]
-
A.
mythologicalLocation
Indicates that the subject is a place or setting that exists within mythology, legends, or folklore rather than in historical or physical reality.
-
B.
typeOfLocationInMyths
chosen
Indicates that a location is classified by the kind of place it is within the context of myths or mythological narratives.
-
C.
worldType
Indicates the classification or category of world or environment that an entity is associated with.
-
D.
geographicalRegionType
Indicates the specific kind or category of geographical region that an entity belongs to (e.g., continent, country, province, or city).
-
E.
fictionalPlaceType
Indicates that a place is a fictional location and specifies what type or category of fictional place it is.
- 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_69e2fabf26bc8190b191faac8f67065b |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f412a9b64881908ed86b9c9b044635 |
completed | May 1, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:49 a.m.