Triple
T4655563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Margaret of Antioch |
E102399
|
entity |
| Predicate | relics |
P50090
|
FINISHED |
| Object | claimed in various churches in Europe |
—
|
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: claimed in various churches in Europe | Statement: [Saint Margaret of Antioch, relics, claimed in various churches in Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relics Context triple: [Saint Margaret of Antioch, relics, claimed in various churches in Europe]
-
A.
notableRelic
chosen
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
-
B.
relicsLocatedIn
Indicates that certain relics are situated, stored, or found within a specific location.
-
C.
containsRelic
Indicates that one entity holds, includes, or has within it a relic.
-
D.
remnants
Indicates that parts or traces of something remain after the main portion has been removed, used, or destroyed.
-
E.
culturalRemains
Indicates that one entity consists of or contains physical or material traces left by a culture, such as artifacts, structures, or other archaeological evidence.
- 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd6317ba70819089145766d3462e57 |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:14 p.m.