Triple
T35914474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cult of Gloriana |
E1038706
|
entity |
| Predicate | developedInKingdom |
P9365
|
FINISHED |
| Object | Kingdom of England |
—
|
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: Kingdom of England | Statement: [Cult of Gloriana, developedInKingdom, Kingdom of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedInKingdom Context triple: [Cult of Gloriana, developedInKingdom, Kingdom of England]
-
A.
kingdomAssociatedWith
Indicates a relationship where something is connected or related to a particular kingdom, such as belonging to, originating from, or being governed by that kingdom.
-
B.
recognizedAsKingdom
Indicates that an entity is formally acknowledged or classified as a kingdom within a given system or context.
-
C.
foundedKingdom
Indicates that an entity established or created a kingdom as its founder.
-
D.
developedInRegion
chosen
Indicates that something was created, produced, or brought into existence within a specified geographic region.
-
E.
kingdomDomain
Indicates that a kingdom is part of, or belongs within, a particular higher-level domain.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 3, 2026, 4:07 p.m.