Triple
T31749905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryneich |
E810385
|
entity |
| Predicate | hasPoliticalType |
P1815
|
FINISHED |
| Object | kingdom |
—
|
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: kingdom | Statement: [Bryneich, hasPoliticalType, kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliticalType Context triple: [Bryneich, hasPoliticalType, kingdom]
-
A.
hasPoliticalCharacteristic
Indicates that an entity possesses a specific political attribute, quality, or affiliation.
-
B.
hasPoliticalComponent
Indicates that something includes, involves, or is influenced by political factors, interests, or considerations.
-
C.
hasPoliticalRole
Indicates that an entity holds, has held, or is assigned a specific political office, function, or position in relation to another entity or context.
-
D.
hasPolity
chosen
Indicates that one entity possesses, controls, or is associated with a particular political organization, governance structure, or state-like authority.
-
E.
hasPoliticalPower
Indicates that one entity holds authority or influence to make, shape, or enforce political decisions over another entity or within a political system.
- 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_69f348e233cc819083b6695f70cd75d8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: April 30, 2026, 11:27 p.m.