Triple
T31810423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Enchancia |
E811987
|
entity |
| Predicate | hasRoyalStaff |
P193844
|
FINISHED |
| Object | Baileywick |
—
|
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: Baileywick | Statement: [Kingdom of Enchancia, hasRoyalStaff, Baileywick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoyalStaff Context triple: [Kingdom of Enchancia, hasRoyalStaff, Baileywick]
-
A.
hasRoyalGuard
Indicates that an entity is protected or served by a designated royal guard or group of royal guards.
-
B.
hasRoyalStatus
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
-
C.
hasRoyalRankScope
Indicates that a royal rank or title is valid, applicable, or recognized only within a specified scope, such as a particular domain, territory, or context.
-
D.
hasRoyalSymbol
Indicates that an entity possesses or is associated with a symbol representing royalty or royal authority.
-
E.
hasRoyalCircle
Indicates that an entity belongs to, is part of, or is associated with a royal or monarch’s inner circle or court.
- F. None of above. chosen
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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fd57b9cdec81908536c4159e375931 |
completed | May 8, 2026, 3:25 a.m. |
Created at: April 30, 2026, 11:43 p.m.