Triple
T11847145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Or Yehuda |
E281806
|
entity |
| Predicate | hasMunicipalFlag |
P101829
|
FINISHED |
| Object | Flag of Or Yehuda |
—
|
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: Flag of Or Yehuda | Statement: [Or Yehuda, hasMunicipalFlag, Flag of Or Yehuda]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalFlag Context triple: [Or Yehuda, hasMunicipalFlag, Flag of Or Yehuda]
-
A.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
-
B.
hasMunicipalDistrict
Indicates that an administrative entity includes or is divided into one or more municipal districts as its subordinate units.
-
C.
isMunicipalStatus
Indicates that an entity possesses a specific legally defined municipal status or classification within a governmental or administrative system.
-
D.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
E.
hasMunicipalLevel
Indicates that an entity is associated with a specific level or tier within a municipal (local government) hierarchy.
- F. None of above. chosen
Provenance (4 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65c72088190b8de9550c455b788 |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.