Triple
T4082015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giuseppe Piermarini |
E87496
|
entity |
| Predicate | influenceScope |
P2828
|
FINISHED |
| Object | across Europe |
—
|
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: across Europe | Statement: [Giuseppe Piermarini, influenceScope, across Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: influenceScope Context triple: [Giuseppe Piermarini, influenceScope, across Europe]
-
A.
typeOfInfluence
Indicates the specific nature or category of influence that one entity exerts on another.
-
B.
sphereOfInfluence
chosen
Indicates the area or domain within which an entity exerts significant control, impact, or authority over others.
-
C.
placeOfInfluence
Indicates the location or area where an entity exerts significant impact, authority, or cultural, social, or intellectual influence.
-
D.
scopeOfContribution
Indicates the specific area, domain, or extent within which an entity’s contribution or involvement applies.
-
E.
seeksToInfluence
Indicates an entity’s intention or effort to affect, shape, or alter another entity’s behavior, decisions, or state.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc77dab481909bcf197daf2def59 |
completed | March 9, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.