Triple
T24526400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fourth Aliyah |
E606680
|
entity |
| Predicate | mainPlaceOfSettlement |
P55226
|
FINISHED |
| Object | Tel Aviv |
—
|
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: Tel Aviv | Statement: [Fourth Aliyah, mainPlaceOfSettlement, Tel Aviv]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPlaceOfSettlement Context triple: [Fourth Aliyah, mainPlaceOfSettlement, Tel Aviv]
-
A.
mainMunicipality
Indicates that one municipality serves as the primary or central administrative municipality associated with another entity or area.
-
B.
mainSettlement
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
C.
mainSettlementLocatedOn
Indicates that the primary settlement of an area is situated on or directly adjacent to a specified geographic feature or location.
-
D.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
E.
hasMainPlace
chosen
Indicates that one entity is designated as the primary or central location associated with 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_69e2c4c85778819085f5da9af3569ad5 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:25 a.m.