Triple
T26246550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brechou |
E656459
|
entity |
| Predicate | hasNearbyJurisdiction |
P180481
|
FINISHED |
| Object | Sark Chief Pleas |
—
|
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: Sark Chief Pleas | Statement: [Brechou, hasNearbyJurisdiction, Sark Chief Pleas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyJurisdiction Context triple: [Brechou, hasNearbyJurisdiction, Sark Chief Pleas]
-
A.
hasAdjacentJurisdiction
Indicates that one jurisdiction directly borders or is immediately next to another jurisdiction.
-
B.
territorialJurisdictionIncludes
Indicates that one authority’s territorial jurisdiction encompasses or extends over a specified geographic area or location.
-
C.
hasNearbyCounty
Indicates that one county is geographically close to or directly adjacent to another county.
-
D.
hasJurisdictionBoundary
Indicates that a defined boundary marks the geographic or legal limits within which an authority or jurisdiction has power or control.
-
E.
hasNearbyProvince
Indicates that one province is geographically close to or directly adjacent to another province.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 26, 2026, 9:05 p.m.