Triple
T9020525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilica of the Holy Blood |
E215710
|
entity |
| Predicate | relicBroughtInYear |
P73225
|
FINISHED |
| Object | 1150 |
—
|
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: 1150 | Statement: [Basilica of the Holy Blood, relicBroughtInYear, 1150]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relicBroughtInYear Context triple: [Basilica of the Holy Blood, relicBroughtInYear, 1150]
-
A.
notableRelic
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
-
B.
containsRelic
Indicates that one entity holds, includes, or has within it a relic.
-
C.
relicsTranslationDate
chosen
Indicates the date on which the relics were translated or moved from one location to another.
-
D.
relicsLocatedIn
Indicates that certain relics are situated, stored, or found within a specific location.
-
E.
estimatedYearOfCreation
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
- 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_69ca83a38aa88190bf1bb80c4548b5e2 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a421c2c8190abb12c826066fe75 |
completed | April 1, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.