Triple
T1563254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basilica Cistern |
E33374
|
entity |
| Predicate | MedusaHeadsLocation |
P29468
|
FINISHED |
| Object | northwest corner |
—
|
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: northwest corner | Statement: [Basilica Cistern, MedusaHeadsLocation, northwest corner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MedusaHeadsLocation Context triple: [Basilica Cistern, MedusaHeadsLocation, northwest corner]
-
A.
resurrectionPlace
Indicates the location where an entity is brought back to life or restored from death.
-
B.
mythologicalLocation
Indicates that the subject is a place or setting that exists within mythology, legends, or folklore rather than in historical or physical reality.
-
C.
revelationPlace
Indicates the place or location where a revelation, disclosure, or revealing event occurs.
-
D.
majorShrineLocation
Indicates that a major religious shrine is located at or associated with a particular place or geographic location.
-
E.
cultLocation
Indicates that a cult or religious group is based in, practices in, or is primarily associated with a particular location.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a90fccd4b48190a44012888a00af7f |
completed | March 5, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69a907b872f0819096b3df6ad502c63e |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a90fcb8ca48190a9ee50559ba73b22 |
completed | March 5, 2026, 5:08 a.m. |
Created at: March 4, 2026, 7:27 p.m.