Triple
T38037078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | גבעת שמואל |
E949379
|
entity |
| Predicate | מעמד מוניציפלי |
P852
|
FINISHED |
| Object | עירייה |
—
|
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: עירייה | Statement: [גבעת שמואל, מעמד מוניציפלי, עירייה]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: מעמד מוניציפלי Context triple: [גבעת שמואל, מעמד מוניציפלי, עירייה]
-
A.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
B.
municipality
chosen
Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
-
C.
cityMayor
Indicates that one entity serves as the mayor (chief elected municipal official) of the city represented by the other entity.
-
D.
municipalScope
Indicates that something falls within the authority, jurisdiction, or functional domain of a municipality or local city government.
-
E.
municipalTransition
Indicates a change in a municipality’s status, structure, or governance, such as incorporation, merger, dissolution, or boundary reorganization.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.