Triple
T20114033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beit Jann |
E490406
|
entity |
| Predicate | localCouncilStatusSince |
P71032
|
FINISHED |
| Object | 1964 |
—
|
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: 1964 | Statement: [Beit Jann, localCouncilStatusSince, 1964]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: localCouncilStatusSince Context triple: [Beit Jann, localCouncilStatusSince, 1964]
-
A.
gainedLocalCouncilStatusInYear
chosen
Indicates that an entity obtained official local council status in the specified year.
-
B.
districtCouncil
Indicates that an entity serves as, or is governed by, a district-level council within a larger administrative or political structure.
-
C.
hasMunicipalCouncilUntil
Indicates that a municipal council served as the governing body of an entity up to a specified end date or point in time.
-
D.
currentLocalAuthority
Indicates that one entity is the local governing authority that currently has jurisdiction over another entity or area.
-
E.
countyCouncilEstablished
Indicates that a county council has been formally created or brought into existence for a given county or jurisdiction.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666e31af081908d8e0c867c388a73 |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:29 p.m.