Triple
T25930734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minquiers and Ecrehos case |
E653430
|
entity |
| Predicate | relatedStateTerritory |
P110989
|
FINISHED |
| Object | Jersey |
—
|
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: Jersey | Statement: [Minquiers and Ecrehos case, relatedStateTerritory, Jersey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedStateTerritory Context triple: [Minquiers and Ecrehos case, relatedStateTerritory, Jersey]
-
A.
traditionalStateOrTerritory
Indicates that an entity is located within, associated with, or belongs to a traditional state or territory as defined by historical or customary boundaries.
-
B.
stateOfTerritory
chosen
Indicates the political or administrative state that has authority over a given territory.
-
C.
stateOrTerritory
Indicates that one entity is a state or territory that is politically or administratively associated with another entity.
-
D.
borderingStateOrTerritory
Indicates that one state or territory shares a common boundary with another state or territory.
-
E.
endStateOrTerritory
Indicates the resulting state or territory that an entity or process ends up in after a change, action, or transition.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 22, 2026, 8:36 a.m.