Triple
T28798857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kourou River |
E727170
|
entity |
| Predicate | locatedInOverseasRegionOf |
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: [Kourou River, locatedInOverseasRegionOf, France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInOverseasRegionOf Context triple: [Kourou River, locatedInOverseasRegionOf, France]
-
A.
locatedInOverseasCountry
Indicates that an entity is situated in a country that is overseas relative to a given reference location or jurisdiction.
-
B.
overseasRegionOf
chosen
Indicates that one region is an overseas territory or administrative division belonging to another country or primary region.
-
C.
containsOverseasRegionOrCollectivity
Indicates that an entity includes within its jurisdiction or composition at least one overseas region or collectivity.
-
D.
hasOverseasPresenceIn
Indicates that an entity maintains operations, offices, or activities in a foreign country or region.
-
E.
overseasCountry
Indicates that one entity is a country located outside the primary or reference country associated with the other entity.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69ffb1f0b03c81909ddb81f07ce74e88 |
completed | May 9, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ffb1662b2481908582e0612744f4c5 |
completed | May 9, 2026, 10:12 p.m. |
Created at: April 28, 2026, 6:26 a.m.