Triple
T25979015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Christophe |
E646018
|
entity |
| Predicate | mainTownHistoricalFrenchSide |
P143877
|
FINISHED |
| Object | Basseterre |
—
|
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: Basseterre | Statement: [Saint-Christophe, mainTownHistoricalFrenchSide, Basseterre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainTownHistoricalFrenchSide Context triple: [Saint-Christophe, mainTownHistoricalFrenchSide, Basseterre]
-
A.
borderTownOnFrenchSide
Indicates that a town is located on the French side of a border shared with another country.
-
B.
historicalMainTown
chosen
Indicates that one place served as the primary or principal town for another place during a specific historical period.
-
C.
FrenchSide
Indicates that an entity is positioned on, associated with, or belongs to the French side of a border, division, or relationship.
-
D.
containsHistoricFort
Indicates that a place or area includes within its boundaries a historic fort.
-
E.
containsHistoricTown
Indicates that one entity geographically includes or encompasses a town that has recognized historical significance.
- 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_69e77e881fc08190ba1c8dc7e2a07f97 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 22, 2026, 8:53 a.m.