Triple
T14033933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soldaia |
E337660
|
entity |
| Predicate | hasAlternativeName |
P39
|
FINISHED |
| Object | Soldaia colony |
E71874
|
NE 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: Soldaia colony | Statement: [Soldaia, hasAlternativeName, Soldaia colony]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Soldaia colony Context triple: [Soldaia, hasAlternativeName, Soldaia colony]
-
A.
Alexandrowka colony
chosen
The Alexandrowka colony is a historic 19th-century Russian-style settlement in Potsdam, Germany, built for Russian singers in Prussian service and now recognized as a UNESCO World Heritage Site.
-
B.
Kolonia
Kolonia is the main urban center and former administrative hub on the island of Pohnpei in the Federated States of Micronesia.
-
C.
Colonia
Colonia is the historical Latin name for the German city of Cologne, reflecting its origins as a Roman colony.
-
D.
Colonia
Colonia is the main administrative and population center of Yap State in the Federated States of Micronesia, located on the island of Yap.
-
E.
Colonia Maza
Colonia Maza is a neighborhood in Mexico City located within the central borough of Cuauhtémoc.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fac71188190a586049405f1071e |
completed | April 14, 2026, 12:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fbc339d53c8190a9cd7027a716ff5f |
completed | May 6, 2026, 10:39 p.m. |
Created at: April 9, 2026, 10:20 p.m.