Triple
T25722375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modi'in Illit |
E645025
|
entity |
| Predicate | settlementBloc |
P89140
|
FINISHED |
| Object | Modi'in Illit bloc |
—
|
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: Modi'in Illit bloc | Statement: [Modi'in Illit, settlementBloc, Modi'in Illit bloc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settlementBloc Context triple: [Modi'in Illit, settlementBloc, Modi'in Illit bloc]
-
A.
formedAsSettlementBloc
chosen
Indicates that an area or group of areas has been organized or designated collectively as a single settlement bloc.
-
B.
settlementWith
Indicates a relationship where one party reaches or maintains a settlement or agreement with another party, typically resolving a dispute or claim.
-
C.
settlementAct
Indicates the act of resolving a dispute or obligation, typically by reaching and formalizing a settlement between involved parties.
-
D.
settlementModel
Indicates a relationship where one entity serves as a model, template, or prototypical example for the structure, organization, or characteristics of a settlement associated with another entity.
-
E.
settlementState
Indicates the state or status of a settlement process or transaction at a given point in time.
- 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_69e77e8476fc8190bd5e9d05b89fad0a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc683cd48190bf4bab9cb8de691a |
completed | May 2, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69f480824a1c81908a8a492eedbc2596 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 10:04 p.m.