Triple
T13809840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clipperton Island |
E331857
|
entity |
| Predicate | hasHistoricalClaim |
P64707
|
FINISHED |
| Object | claimed by France |
—
|
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: claimed by France | Statement: [Clipperton Island, hasHistoricalClaim, claimed by France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalClaim Context triple: [Clipperton Island, hasHistoricalClaim, claimed by France]
-
A.
historicalClaim
Indicates that an entity asserts or presents a statement about past events or conditions as a matter of historical fact.
-
B.
historicalClaimBy
chosen
Indicates that a particular historical assertion or interpretation is attributed to a specific source or agent.
-
C.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
D.
hasHistoricalDetail
Indicates that something includes or is associated with specific information about past events, contexts, or developments.
-
E.
hasReclamationHistory
Indicates that an entity has a documented record of land or resource reclamation activities associated with it.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de026ff6b481908066d6bf27064417 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.