Triple
T16407131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giulio Borghese |
E398462
|
entity |
| Predicate | nobleFamilyInfluence |
P106712
|
FINISHED |
| Object | influential in Roman politics |
—
|
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: influential in Roman politics | Statement: [Giulio Borghese, nobleFamilyInfluence, influential in Roman politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleFamilyInfluence Context triple: [Giulio Borghese, nobleFamilyInfluence, influential in Roman politics]
-
A.
nobleHouseInfluence
chosen
Indicates the degree to which a noble house exerts power, control, or sway over people, events, or territories.
-
B.
associatedNobleFamily
Indicates a relationship where an entity is linked or connected to a particular noble family, typically by heritage, allegiance, or formal association.
-
C.
usedByNobleFamily
Indicates that something is employed, possessed, or otherwise utilized by a noble family.
-
D.
motherNobleFamily
Indicates that a person’s mother belongs to a specified noble family or house.
-
E.
notableNoble
Indicates that an entity is a noble who is particularly prominent, distinguished, or widely recognized in some notable way.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327d36b808190b6b8c412ae0d2faa |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.