Triple
T28520824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Furball |
E721758
|
entity |
| Predicate | storyWorldElement |
P116836
|
FINISHED |
| Object | kingdom |
—
|
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: kingdom | Statement: [Princess Furball, storyWorldElement, kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyWorldElement Context triple: [Princess Furball, storyWorldElement, kingdom]
-
A.
storyWorld
Indicates the fictional universe or narrative setting within which a story, event, or character exists or takes place.
-
B.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
C.
hasFictionalSettingElement
chosen
Indicates that something includes or is associated with a specific element or component of a fictional setting.
-
D.
storySettingEvent
Indicates that an event takes place within, or helps define, the setting or background context of a story.
-
E.
setInFictionalLocation
Indicates that an event, story, or narrative takes place within a fictional or imagined location rather than a real-world setting.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 3:20 a.m.