Triple
T17839407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giuseppe Borghese |
E445481
|
entity |
| Predicate | saidToBeFrom |
P21703
|
FINISHED |
| Object | Italian aristocracy |
—
|
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: Italian aristocracy | Statement: [Giuseppe Borghese, saidToBeFrom, Italian aristocracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saidToBeFrom Context triple: [Giuseppe Borghese, saidToBeFrom, Italian aristocracy]
-
A.
allegedBirthRegion
chosen
Indicates the region where an entity is claimed or reported to have been born, without asserting that this birthplace is verified as fact.
-
B.
wasAdministrativeRegionFrom
Indicates that an entity served as an administrative region of another entity starting from a specified point in time.
-
C.
proclaimedFrom
Indicates that something was formally announced or declared originating from a particular source, place, or authority.
-
D.
adoptedFrom
Indicates that an entity has been taken into guardianship, ownership, or use from another source or origin.
-
E.
hasTypicalGeographicOrigin
Indicates that an entity is commonly or characteristically associated with originating from a particular geographic location.
- 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48d2a570c81909787296bde7e795c |
completed | April 19, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:16 a.m.