Triple
T35424679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bethlehem of Galilee |
E1023885
|
entity |
| Predicate | laterResettledBy |
P183926
|
FINISHED |
| Object | Jewish settlers |
—
|
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: Jewish settlers | Statement: [Bethlehem of Galilee, laterResettledBy, Jewish settlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterResettledBy Context triple: [Bethlehem of Galilee, laterResettledBy, Jewish settlers]
-
A.
resettledBy
Indicates that an entity has been moved or established anew in a location or context by another agent or authority.
-
B.
resettledFrom
Indicates that an entity has moved or been relocated from a previous place of residence or origin to a new location.
-
C.
resettledAt
Indicates that an entity has moved and established residence or presence at a new location.
-
D.
wasSettledBy
chosen
Indicates that a place or region came to be inhabited or established through the actions of a particular person, group, or population.
-
E.
settledAs
Indicates that one entity has been resolved, finalized, or agreed upon in the form or status of another entity.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00694f72888190983fee7d687a6daa |
completed | May 10, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_6a00685dbf44819098ea0c86bb9e50d8 |
completed | May 10, 2026, 11:13 a.m. |
Created at: May 3, 2026, 4:03 p.m.