Triple
T24739719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tonoas Island |
E618518
|
entity |
| Predicate | wasPreviouslyColonizedBy |
P160
|
FINISHED |
| Object | Germany |
—
|
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: Germany | Statement: [Tonoas Island, wasPreviouslyColonizedBy, Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPreviouslyColonizedBy Context triple: [Tonoas Island, wasPreviouslyColonizedBy, Germany]
-
A.
wasLaterColonizedBy
Indicates that one entity became a colony of another entity at a later point in time than some referenced event or colonization.
-
B.
wasColonyOf
chosen
Indicates that one entity functioned as a colony under the political control or administration of another entity.
-
C.
endedAsColony
Indicates that an entity ultimately ceased to exist as an independent polity and finished its historical trajectory under colonial rule by another power.
-
D.
hadColonyOn
Indicates that one entity established or possessed a colony located on another entity (typically a territory, planet, or celestial body).
-
E.
usedToBeHomelandOf
Indicates that a place previously served as the homeland or native territory of a particular group or entity, but no longer does so.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:04 a.m.