Triple
T11915919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edwardian court |
E283519
|
entity |
| Predicate | hasDynasticPolitics |
P45085
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Edwardian court, hasDynasticPolitics, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDynasticPolitics Context triple: [Edwardian court, hasDynasticPolitics, true]
-
A.
dynasticState
Indicates a relationship where a state or political entity is ruled or defined by a hereditary dynasty or ruling family.
-
B.
hasDynasticSignificance
Indicates that something holds importance or influence within the context of a dynasty’s continuity, status, or historical legacy.
-
C.
hasDynasticOrder
Indicates that there exists a specific sequence or hierarchy of dynasties or ruling lines associated with the subject.
-
D.
hasMajorDynasty
Indicates that an entity (such as a region, state, or historical period) is associated with or ruled by a particular major dynasty.
-
E.
dynasticContext
chosen
Indicates the historical or political circumstances defined by a particular ruling dynasty under which the related entities or events are situated.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8deb14881909b65a1f159aec65f |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3632ac8190b13e53c2b5db7125 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.