Triple
T26790845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christ's Tears over Jerusalem |
E670512
|
entity |
| Predicate | symbolicSetting |
P1957
|
FINISHED |
| Object | Jerusalem |
—
|
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: Jerusalem | Statement: [Christ's Tears over Jerusalem, symbolicSetting, Jerusalem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolicSetting Context triple: [Christ's Tears over Jerusalem, symbolicSetting, Jerusalem]
-
A.
coversSetting
Indicates that one entity includes or addresses a particular setting or context within its scope.
-
B.
indicatedSetting
Indicates that one entity specifies, denotes, or points out a particular setting or configuration associated with another entity.
-
C.
knownAsSettingFor
Indicates that something is recognized or regarded as the typical or notable setting or backdrop for something else.
-
D.
notableSetting
Indicates that a particular place or environment is especially significant or prominent as the context in which an entity is situated or occurs.
-
E.
setting
chosen
Indicates the place, time, or context in which an event, action, or interaction occurs.
- 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 4:16 a.m.