Triple
T29016929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carabella |
E737335
|
entity |
| Predicate | belongsToFictionalWorld |
P15645
|
FINISHED |
| Object | Majipoor |
—
|
NE NERFINISHED |
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: Majipoor | Statement: [Carabella, belongsToFictionalWorld, Majipoor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToFictionalWorld Context triple: [Carabella, belongsToFictionalWorld, Majipoor]
-
A.
belongsToFictionalRegion
Indicates that an entity is located within, associated with, or under the jurisdiction of a fictional or imaginary geographic region.
-
B.
hasFictionalUniverseElement
chosen
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
C.
isSetInFictionalUniverse
Indicates that a narrative work takes place within a specific fictional universe or setting.
-
D.
hasFictionalUniverseProperty
Indicates that a fictional universe possesses a specific characteristic, attribute, or property.
-
E.
belongsToFictionalContinent
Indicates that something is located on, associated with, or a part of a specific fictional continent within an imagined world.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 28, 2026, 9:46 a.m.