Triple
T36761321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tzippori |
E908206
|
entity |
| Predicate | hasModernSettlementType |
P128342
|
FINISHED |
| Object | moshav |
—
|
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: moshav | Statement: [Tzippori, hasModernSettlementType, moshav]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernSettlementType Context triple: [Tzippori, hasModernSettlementType, moshav]
-
A.
hasTraditionalSettlementType
Indicates that an entity is associated with a specific traditional or historically established type of human settlement (e.g., village, town, hamlet).
-
B.
hasHumanSettlement
Indicates that a location or area contains or is the site of a human settlement, such as a town, village, or city.
-
C.
modernSettlement
chosen
Indicates that the subject is a contemporary or currently existing human settlement located at the object.
-
D.
isOneOfOlderSettlementsIn
Indicates that an entity is among the earlier or historically older settlements located within a specified area or region.
-
E.
hasModernTerritory
Indicates that an entity (typically a historical or former polity) corresponds geographically to the present-day territory of another entity (usually a modern state or region).
- 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_69f76e779bec8190be0e1f87a131e0f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff7595c9bc8190982c6e6e07a0c78f |
completed | May 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69ff715432a88190a25670d26614bde2 |
completed | May 9, 2026, 5:39 p.m. |
Created at: May 3, 2026, 4:12 p.m.