Triple
T27327294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zawichost County |
E689688
|
entity |
| Predicate | hadJudicialCenter |
P95712
|
FINISHED |
| Object | Zawichost |
—
|
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: Zawichost | Statement: [Zawichost County, hadJudicialCenter, Zawichost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadJudicialCenter Context triple: [Zawichost County, hadJudicialCenter, Zawichost]
-
A.
hadJudicialCounterpart
Indicates that one legal or judicial entity corresponded to, or was matched by, another entity serving an equivalent judicial role or function.
-
B.
hadJudicialFunction
Indicates that an entity exercised or was assigned an official judicial role, authority, or responsibility in relation to another entity or context.
-
C.
hadRulingSeat
Indicates that an entity held an official position of authority or judgment within a governing or decision-making body.
-
D.
hasJurisdictionalCenter
chosen
Indicates that an administrative or legal authority is associated with a specific central location from which its jurisdiction is exercised or managed.
-
E.
hasJudiciary
Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f627eea1d08190aa3733b460c43b6e |
completed | May 2, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 11:36 a.m.