Triple
T30617719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | שִׁלֹה |
E779357
|
entity |
| Predicate | statusInJeremiah |
P195278
|
FINISHED |
| Object | example of destroyed sanctuary |
—
|
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: example of destroyed sanctuary | Statement: [שִׁלֹה, statusInJeremiah, example of destroyed sanctuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInJeremiah Context triple: [שִׁלֹה, statusInJeremiah, example of destroyed sanctuary]
-
A.
statusInSira
Indicates the status or standing that an entity holds within the Sira system or classification.
-
B.
statusInNippur
Indicates the social, legal, or administrative standing an entity holds specifically within the city or jurisdiction of Nippur.
-
C.
jerseyStatus
Indicates the current condition, availability, or usage state of a jersey in relation to an entity.
-
D.
statusInRevelation
Indicates the role, condition, or standing that an entity holds within the context of a particular revelation or revealed message.
-
E.
statusInYomi
Indicates the role, rank, or condition an entity holds within the realm or context of Yomi.
- 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdb45537288190b6791078d4a6899f |
completed | May 8, 2026, 10 a.m. |
| PD | Predicate disambiguation | batch_69fdb39ad96481908376d7def9fafc13 |
completed | May 8, 2026, 9:57 a.m. |
| PDg | Predicate description generation | batch_69fdb4544b548190b8971f8055d48caa |
completed | May 8, 2026, 10 a.m. |
Created at: April 29, 2026, 8:26 p.m.