Triple
T35014551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Candy Castle |
E1010017
|
entity |
| Predicate | countryInFictionalWorld |
P186947
|
FINISHED |
| Object | Candy Kingdom |
E308908
|
NE 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: Candy Kingdom | Statement: [Candy Castle, countryInFictionalWorld, Candy Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryInFictionalWorld Context triple: [Candy Castle, countryInFictionalWorld, Candy Kingdom]
-
A.
locatedInFictionalCountry
Indicates that an entity exists or is situated within a country that is fictional rather than real.
-
B.
countryOfFictionalContext
Indicates that a work of fiction is primarily set in, or contextually associated with, a particular country.
-
C.
nationalityOfFictionalSetting
Indicates that a fictional setting is associated with, or belongs to, a particular nationality or country.
-
D.
fictionalCountryMentioned
Indicates that a fictional or imaginary country is referenced or discussed in relation to an entity.
-
E.
countryOfFictionalRepresentation
chosen
Indicates that one entity is the country in which another entity (such as a work or character) is fictionally set or represented.
- F. None of above.
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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a01a0b63d148190b10206509c0a0a5b |
completed | May 11, 2026, 9:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37cfdc245c81909be620c52cc1dba7 |
completed | June 21, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_6a01a0245d4c8190a3c3fbbe83f0389d |
completed | May 11, 2026, 9:23 a.m. |
Created at: May 3, 2026, 4:01 p.m.