Triple
T25366804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrondissement of Cayenne |
E632821
|
entity |
| Predicate | isOverseasRegionOf |
P55603
|
FINISHED |
| Object | France |
—
|
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: France | Statement: [Arrondissement of Cayenne, isOverseasRegionOf, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOverseasRegionOf Context triple: [Arrondissement of Cayenne, isOverseasRegionOf, France]
-
A.
overseasRegionOf
chosen
Indicates that one region is an overseas territory or administrative division belonging to another country or primary region.
-
B.
containsOverseasRegionOrCollectivity
Indicates that an entity includes within its jurisdiction or composition at least one overseas region or collectivity.
-
C.
isInOverseasCollectivity
Indicates that one entity is located within, or belongs administratively to, an overseas collectivity of another entity.
-
D.
overseasCountry
Indicates that one entity is a country located outside the primary or reference country associated with the other entity.
-
E.
hasOverseasTerritory
Indicates that one entity possesses or controls a territory located outside its own primary geographic or sovereign domain.
- 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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4a10eb1748190aa576850282c808d |
completed | May 1, 2026, 12:48 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:37 p.m.