Triple
T33518326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess of DunBroch |
E858432
|
entity |
| Predicate | countryOfFictionalRealm |
P143704
|
FINISHED |
| Object | Scotland |
—
|
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: Scotland | Statement: [Princess of DunBroch, countryOfFictionalRealm, Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryOfFictionalRealm Context triple: [Princess of DunBroch, countryOfFictionalRealm, Scotland]
-
A.
countryOfFictionalContext
Indicates that a work of fiction is primarily set in, or contextually associated with, a particular country.
-
B.
nationalityOfFictionalSetting
Indicates that a fictional setting is associated with, or belongs to, a particular nationality or country.
-
C.
countryOfFictionalEmpire
Indicates the real-world country in which a fictional empire is located, originates, or is primarily associated.
-
D.
countryOfFictionalMonarchy
chosen
Indicates the real-world country in which a fictional monarchy is located or to which it belongs.
-
E.
locatedInFictionalCountry
Indicates that an entity exists or is situated within a country that is fictional rather than real.
- 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_69f349781c6c819082c516b260efe7e2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00bcfed6448190b2e816bbe7c61c55 |
completed | May 10, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_6a00bc7be24c81908ba5c1957edd2c10 |
completed | May 10, 2026, 5:12 p.m. |
Created at: May 1, 2026, 1:39 a.m.