Triple
T1485149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chausey |
E29447
|
entity |
| Predicate | historicalDispute |
P2746
|
FINISHED |
| Object | Anglo-French maritime context |
—
|
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: Anglo-French maritime context | Statement: [Chausey, historicalDispute, Anglo-French maritime context]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalDispute Context triple: [Chausey, historicalDispute, Anglo-French maritime context]
-
A.
historicallyContestedBy
chosen
Indicates that two or more parties have disputed or challenged control, ownership, or interpretation of something over a period of history.
-
B.
historicalClaim
Indicates that an entity asserts or presents a statement about past events or conditions as a matter of historical fact.
-
C.
historicallyOpposedBy
Indicates that one entity has been the target of opposition, resistance, or antagonism from another entity over a historical period.
-
D.
hasDisputeHistory
Indicates that there has been at least one prior dispute or conflict involving the related entities.
-
E.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6a011f0819086e9ee517ed6d29f |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c486eacc81909c272f9bdf50a7c3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.