Triple
T27493557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daphne Palace |
E693957
|
entity |
| Predicate | ceremonialAxisWith |
P162449
|
FINISHED |
| Object | Hagia Sophia |
—
|
NE NERFINISHED |
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: Hagia Sophia | Statement: [Daphne Palace, ceremonialAxisWith, Hagia Sophia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialAxisWith Context triple: [Daphne Palace, ceremonialAxisWith, Hagia Sophia]
-
A.
ceremonialSymbol
Indicates that one entity serves as a symbol used in a formal or ritual ceremony for another entity or concept.
-
B.
ceremonialAction
Indicates an action performed as part of a formal ceremony or ritual, typically following prescribed traditions or symbolic procedures.
-
C.
ceremonialFocus
Indicates that one entity serves as the central object, site, or theme around which a ceremony or ritual is organized or directed.
-
D.
ceremonialFeatures
Indicates that something possesses attributes, elements, or characteristics specifically associated with ceremonies or ritual practices.
-
E.
ceremonialAssociation
Indicates a relationship where entities are linked through participation in, role within, or connection to a formal ceremony or ritual event.
- 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_69ef5382b9648190be0b1ef2ad5d043c |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62e8bdb9c81909ec001884084e075 |
completed | May 2, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f624c006788190a2f4d5015c96463f |
completed | May 2, 2026, 4:22 p.m. |
Created at: April 27, 2026, 1:06 p.m.