Triple
T5053029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carolingian aristocracy |
E113830
|
entity |
| Predicate | maintainsPowerThrough |
P60897
|
FINISHED |
| Object | oaths of fidelity |
—
|
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: oaths of fidelity | Statement: [Carolingian aristocracy, maintainsPowerThrough, oaths of fidelity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainsPowerThrough Context triple: [Carolingian aristocracy, maintainsPowerThrough, oaths of fidelity]
-
A.
reservesPowerTo
Indicates that one party retains or explicitly keeps for itself the authority or right to exercise a particular power or function, rather than granting it to others.
-
B.
hasPowerSource
Indicates that an entity derives its operational energy or functionality from a specified power source.
-
C.
inPowerDuring
Indicates that an entity holds a position of authority or governance throughout a specified time period.
-
D.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
-
E.
hasPowerRegulator
Indicates that an entity is equipped with or connected to a power regulator component that controls or stabilizes its electrical power.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7428d7a88190b990aedae390acbe |
completed | March 20, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd73089f548190834103366e24ab40 |
completed | March 20, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:38 p.m.