Triple
T29619198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Protasius |
E754947
|
entity |
| Predicate | relicsDiscoveredIn |
P36131
|
FINISHED |
| Object | Milan |
—
|
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: Milan | Statement: [Saint Protasius, relicsDiscoveredIn, Milan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relicsDiscoveredIn Context triple: [Saint Protasius, relicsDiscoveredIn, Milan]
-
A.
relicsLocatedIn
chosen
Indicates that certain relics are situated, stored, or found within a specific location.
-
B.
relicsDiscoveryYear
Indicates the year in which the relics were discovered.
-
C.
relicDiscovery
Indicates the event or relationship in which an entity finds or uncovers a relic.
-
D.
relicsAssociatedWith
Indicates a relationship where certain relics are connected or linked to a particular entity, context, or subject (such as a person, place, event, or tradition).
-
E.
discoveredRemainsIn
Indicates that one entity found or uncovered the physical remains of another entity at a specific 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e23382081908e50428ba103b2e8 |
completed | May 2, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:33 p.m.