Triple
T5046207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pietro Bernini |
E113671
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Pietro |
E29219
|
NE 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: Pietro | Statement: [Pietro Bernini, givenName, Pietro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pietro Context triple: [Pietro Bernini, givenName, Pietro]
-
A.
Pietro
chosen
Pietro is the Italian given name equivalent to "Peter," commonly used in Italy and among Italian-speaking communities.
-
B.
Paolo
Paolo is the Italian form of the given name Paul, commonly used in Italy and other Italian-speaking communities.
-
C.
Giovanni
Giovanni was the birth name of Pope Leo X, the influential early 16th-century head of the Catholic Church and a prominent patron of Renaissance art and culture.
-
D.
Giovanni
Giovanni is the Italian form of the given name John, widely used in Italy and among Italian-speaking communities.
-
E.
Giovanni
Giovanni was the birth name of Pope Julius III, a 16th-century head of the Catholic Church and ruler of the Papal States.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73fe99688190961708f5d8eb6bff |
completed | March 20, 2026, 4:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf186790248190bc94cfbecf3cfe73 |
completed | March 21, 2026, 10:15 p.m. |
Created at: March 20, 2026, 1:37 p.m.