Triple
T37186335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maxi Trial against Cosa Nostra |
E921330
|
entity |
| Predicate | keyMagistrate |
P128125
|
FINISHED |
| Object | Giovanni Falcone |
—
|
NE NERFINISHED |
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: Giovanni Falcone | Statement: [Maxi Trial against Cosa Nostra, keyMagistrate, Giovanni Falcone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyMagistrate Context triple: [Maxi Trial against Cosa Nostra, keyMagistrate, Giovanni Falcone]
-
A.
magistrateOf
Indicates that a person holds the official position or role of magistrate in relation to a particular jurisdiction, institution, or group.
-
B.
hasMagistrate
chosen
Indicates that an entity is under the authority, jurisdiction, or oversight of a specific magistrate.
-
C.
magistrateJudgeTerm
Indicates that a magistrate judge holds or serves a specific judicial term or period of office.
-
D.
keyRoyalMinister
Indicates that the subject serves as the primary or principal royal minister to the referenced monarch or royal authority.
-
E.
heldMagistracies
Indicates that one entity occupied or served in official magistrate positions or offices in relation to another entity or political body.
- 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_69f76ea250bc819083f28d81de25cd0c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.