Triple
T34748157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St George of Choziba |
E1001693
|
entity |
| Predicate | locatedInHagiography |
P40
|
FINISHED |
| Object | Palestinian monastic tradition |
—
|
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: Palestinian monastic tradition | Statement: [St George of Choziba, locatedInHagiography, Palestinian monastic tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInHagiography Context triple: [St George of Choziba, locatedInHagiography, Palestinian monastic tradition]
-
A.
locatedInHolyTown
Indicates that an entity is situated within a town that is considered holy or religiously significant.
-
B.
statusInHagiography
Indicates the role or standing an individual holds within a hagiographic account (such as saint, author, subject, or related figure).
-
C.
veneratedAt
Indicates that an entity is honored, revered, or worshipped at a particular place or institution.
-
D.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
E.
religiousFigureBornHere
Indicates that a notable religious figure was born at this location.
- 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_69f76db0367081909b57c50a7fb03025 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 3:59 p.m.