Triple
T24421004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiryat Luza |
E615722
|
entity |
| Predicate | significantForReligion |
P6906
|
FINISHED |
| Object | Samaritanism |
—
|
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: Samaritanism | Statement: [Kiryat Luza, significantForReligion, Samaritanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significantForReligion Context triple: [Kiryat Luza, significantForReligion, Samaritanism]
-
A.
religionSignificant
chosen
Indicates that a particular religion plays an important or influential role in relation to the referenced entity or context.
-
B.
laterReligiousSignificance
Indicates that the subject acquires or is recognized as having religious importance or sacred status at a time subsequent to the period or context initially under consideration.
-
C.
subjectReligion
Indicates that the subject is associated with, practices, or adheres to a particular religion.
-
D.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
E.
positionInReligion
Indicates the specific role, rank, or office an entity holds within a religious organization or tradition.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a34d3081908d6099365e2e4046 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:14 a.m.