Triple
T36761323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tzippori |
E908206
|
entity |
| Predicate | modernSettlementEstablished |
P116089
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Tzippori, modernSettlementEstablished, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernSettlementEstablished Context triple: [Tzippori, modernSettlementEstablished, 20th century]
-
A.
firstModernSettlementEstablished
Indicates that the subject is the location where the earliest modern-era settlement was founded or established.
-
B.
modernSettlement
Indicates that the subject is a contemporary or currently existing human settlement located at the object.
-
C.
modernSettlementArea
Indicates the geographic area occupied by a settlement in its modern or current form.
-
D.
historicalPeriodOfSettlement
chosen
Indicates the historical time period during which a particular settlement or habitation of a place occurred.
-
E.
secondSettlementFounded
Indicates that an entity established its second settlement at a particular place and/or 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_69f76e779bec8190be0e1f87a131e0f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 3, 2026, 4:12 p.m.