Triple
T36306165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icon of Our Lady of Perpetual Help |
E893947
|
entity |
| Predicate | broughtToRomeCentury |
P54321
|
FINISHED |
| Object | 15th century |
—
|
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: 15th century | Statement: [Icon of Our Lady of Perpetual Help, broughtToRomeCentury, 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broughtToRomeCentury Context triple: [Icon of Our Lady of Perpetual Help, broughtToRomeCentury, 15th century]
-
A.
approximateRomanConquestCentury
Indicates the approximate century in which the Romans conquered or gained control over a given entity.
-
B.
laterRelationToRome
Indicates that one entity occurs or exists at a time later than the reference time associated with Rome.
-
C.
transportedToRomeIn
chosen
Indicates that something or someone was transported or moved to Rome at a particular time or by a particular means.
-
D.
broughtInCentury
Indicates that something was introduced, initiated, or came into existence during a specified century.
-
E.
significanceToRome
Indicates that something holds particular importance, influence, or relevance in relation to Rome.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.