Triple
T8700675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giorgio Perlasca |
E206521
|
entity |
| Predicate | protectedAtLocation |
P84629
|
FINISHED |
| Object | Spanish safe houses in Budapest |
—
|
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: Spanish safe houses in Budapest | Statement: [Giorgio Perlasca, protectedAtLocation, Spanish safe houses in Budapest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectedAtLocation Context triple: [Giorgio Perlasca, protectedAtLocation, Spanish safe houses in Budapest]
-
A.
protectedFor
Indicates that something is safeguarded or preserved specifically for the benefit, use, or rights of a particular entity or purpose.
-
B.
protectedAs
Indicates that one entity is safeguarded, preserved, or kept safe by another entity or under a specified protective status or mechanism.
-
C.
protectedGround
Indicates that one entity has taken action to safeguard or defend another entity or area from harm, damage, or unauthorized interference.
-
D.
protectedAspect
Indicates that one entity is safeguarded, preserved, or kept safe by another entity or mechanism.
-
E.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
- F. None of above. chosen
Provenance (4 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58b27bd48190a5f76111ee657553 |
completed | March 31, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc582412f48190ae819965bfb0e75d |
completed | March 31, 2026, 11:26 p.m. |
Created at: March 30, 2026, 6:34 p.m.