Triple
T32778042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beornwulf of Mercia |
E838271
|
entity |
| Predicate | internalConditionOfRealm |
P194618
|
FINISHED |
| Object | political instability |
—
|
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: political instability | Statement: [Beornwulf of Mercia, internalConditionOfRealm, political instability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internalConditionOfRealm Context triple: [Beornwulf of Mercia, internalConditionOfRealm, political instability]
-
A.
residesInRealm
Indicates that an entity lives or exists within a particular realm or domain.
-
B.
coreCondition
Indicates that something serves as the primary or fundamental condition that must hold for a situation, process, or relationship to apply.
-
C.
overseesRealm
Indicates that one entity has authority or supervisory control over a particular realm, domain, or territory.
-
D.
includesRealm
Indicates that one entity encompasses or contains a particular realm as part of its scope or domain.
-
E.
aidedRealm
Indicates that one entity provided help, support, or assistance to a particular realm or domain.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
| PDg | Predicate description generation | batch_69fd7e35967081909f8bc8389d976ffd |
completed | May 8, 2026, 6:09 a.m. |
Created at: May 1, 2026, 1:13 a.m.