Triple
T29524927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Mora |
E749040
|
entity |
| Predicate | hasSphereOfInfluence |
P2828
|
FINISHED |
| Object | European nobility |
—
|
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: European nobility | Statement: [House of Mora, hasSphereOfInfluence, European nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSphereOfInfluence Context triple: [House of Mora, hasSphereOfInfluence, European nobility]
-
A.
sphereOfInfluence
chosen
Indicates the area or domain within which an entity exerts significant control, impact, or authority over others.
-
B.
hasInfluenceScope
Indicates the range or extent within which an entity’s influence, impact, or authority is effective or applicable.
-
C.
isUnderInfluenceOf
Indicates that one entity is affected, controlled, or significantly shaped by the power, authority, or effect of another entity.
-
D.
hasRegionalInfluenceFrom
Indicates that one entity’s influence, impact, or authority in a region is derived from or shaped by another entity.
-
E.
hasSignificantInfluenceIn
Indicates that one entity exerts a substantial impact or shaping effect on another entity within a particular domain, context, or outcome.
- 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: April 28, 2026, 4:44 p.m.