Triple
T12944892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rokovoko |
E309734
|
entity |
| Predicate | hasFictionalCulture |
P15645
|
FINISHED |
| Object | Polynesian-inspired society |
—
|
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: Polynesian-inspired society | Statement: [Rokovoko, hasFictionalCulture, Polynesian-inspired society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalCulture Context triple: [Rokovoko, hasFictionalCulture, Polynesian-inspired society]
-
A.
hasFictionalUniverseElement
chosen
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
B.
hasFictionalUniverseGenre
Indicates that a fictional universe is associated with a particular genre that characterizes its overall style, themes, or narrative type.
-
C.
hasFictionalUniverseProperty
Indicates that a fictional universe possesses a specific characteristic, attribute, or property.
-
D.
hasFictionalContent
Indicates that something contains or includes material that is imaginary, invented, or not intended to represent real events or facts.
-
E.
hasFictionalInhabitants
Indicates that a place or setting is inhabited by fictional or imaginary beings.
- 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_69d7bdfb57a88190836b743e2825feca |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97db69f548190a1a693bc0d6c191a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 5:43 p.m.