Triple
T6253702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mausoleum of Galla Placidia |
E140107
|
entity |
| Predicate | inscribedUnder |
P69736
|
FINISHED |
| Object | criteria (i)(ii)(iii)(iv) of UNESCO |
—
|
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: criteria (i)(ii)(iii)(iv) of UNESCO | Statement: [Mausoleum of Galla Placidia, inscribedUnder, criteria (i)(ii)(iii)(iv) of UNESCO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscribedUnder Context triple: [Mausoleum of Galla Placidia, inscribedUnder, criteria (i)(ii)(iii)(iv) of UNESCO]
-
A.
inscribedFor
Indicates that something is formally written, engraved, or dedicated for a particular recipient or purpose.
-
B.
inscribedBy
Indicates that one object has another object written, carved, or engraved onto its surface.
-
C.
inscribedTogetherWith
Indicates that one entity is inscribed jointly with another on the same surface, object, or document as part of a single inscription context.
-
D.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
-
E.
circumscribedBy
Indicates that one entity is completely enclosed or bounded on all sides by another entity.
- F. None of above. chosen
Provenance (4 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063625608819081f5422112c80ce5 |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c05707d5408190a1d0fd80414ad957 |
completed | March 22, 2026, 8:54 p.m. |
Created at: March 22, 2026, 4:24 p.m.