Triple
T28239813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adolf III of the Marck |
E711989
|
entity |
| Predicate | meansOfPowerExpansion |
P136123
|
FINISHED |
| Object | feudal alliances |
—
|
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: feudal alliances | Statement: [Adolf III of the Marck, meansOfPowerExpansion, feudal alliances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meansOfPowerExpansion Context triple: [Adolf III of the Marck, meansOfPowerExpansion, feudal alliances]
-
A.
expandedPowerTo
Indicates that one entity has increased or broadened authority, influence, or control over another entity or domain.
-
B.
meansOfPowerAcquisition
chosen
Indicates the method or process through which an entity obtains or gains power or authority.
-
C.
occupationPower
Indicates a relationship where one party holds authoritative control, influence, or dominance over another within the context of an occupation or role.
-
D.
sectorExpansion
Indicates an increase or broadening in the size, scope, or activity level of a particular sector or industry over time.
-
E.
plannedExpansion
Indicates that an entity has a scheduled or intended increase in size, capacity, scope, or presence in the future.
- 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_69efb51ece308190b8c269a057e36652 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f643c3aab88190842770d1bc058c07 |
completed | May 2, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:57 p.m.