Triple
T27214559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom |
E684100
|
entity |
| Predicate | exertsInfluenceOver |
P63153
|
FINISHED |
| Object | neighboring regions |
—
|
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: neighboring regions | Statement: [Kingdom, exertsInfluenceOver, neighboring regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exertsInfluenceOver Context triple: [Kingdom, exertsInfluenceOver, neighboring regions]
-
A.
influencedIn
Indicates that one entity had an effect on or shaped another entity within a specific context, domain, or setting.
-
B.
hasSignificantInfluenceIn
chosen
Indicates that one entity exerts a substantial impact or shaping effect on another entity within a particular domain, context, or outcome.
-
C.
hasRegionalInfluenceFrom
Indicates that one entity’s influence, impact, or authority in a region is derived from or shaped by another entity.
-
D.
politicalInfluenceIn
Indicates that an entity exerts or holds political influence within a specified place, jurisdiction, or political context.
-
E.
politicalPowerInfluencedBy
Indicates that the extent or nature of an entity’s political power is shaped, affected, or determined by another entity or factor.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6261bcb988190ab516bee317a881c |
completed | May 2, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 9:40 a.m.