Triple
T28369364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papazzurri family |
E718581
|
entity |
| Predicate | localInfluence |
P65945
|
FINISHED |
| Object | Roman society |
—
|
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: Roman society | Statement: [Papazzurri family, localInfluence, Roman society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localInfluence Context triple: [Papazzurri family, localInfluence, Roman society]
-
A.
nearbyInfluence
Indicates that one entity affects or exerts influence on another due to being physically or spatially close to it.
-
B.
localImportance
Indicates that something holds particular significance, influence, or priority within a specific, limited context or area rather than globally.
-
C.
localReputation
Indicates the perceived standing, trustworthiness, or esteem an entity holds within a specific local community or area.
-
D.
hasLocalImpact
Indicates that an entity produces effects or consequences within a specific local area or community.
-
E.
influencesCommunity
chosen
Indicates that one entity has an effect on the behavior, attitudes, or conditions of a community.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:58 a.m.