Triple
T26010788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry VI |
E646892
|
entity |
| Predicate | expanded influence in |
P18876
|
FINISHED |
| Object | Italy |
—
|
NE NERFINISHED |
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: Italy | Statement: [Henry VI, expanded influence in, Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expanded influence in Context triple: [Henry VI, expanded influence in, Italy]
-
A.
effectOfExpansion
Indicates the outcome or impact that a particular expansion (such as growth, enlargement, or extension of something) has on another entity or condition.
-
B.
expandedTerritoryTo
chosen
Indicates that one entity has increased the geographic area under its control or influence to include the territory of another entity.
-
C.
incorporatesInfluence
Indicates that one entity integrates or absorbs the influence, ideas, or characteristics of another into itself.
-
D.
hasRegionalInfluenceFrom
Indicates that one entity’s influence, impact, or authority in a region is derived from or shaped by another entity.
-
E.
influenced
Indicates that one entity has affected, shaped, or altered another entity’s state, behavior, or characteristics.
- 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 22, 2026, 9:01 a.m.