Triple
T33106777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiautschou Bay |
E847209
|
entity |
| Predicate | wasColonialLeaseholdOf |
P174108
|
FINISHED |
| Object | German Empire |
—
|
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: German Empire | Statement: [Kiautschou Bay, wasColonialLeaseholdOf, German Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasColonialLeaseholdOf Context triple: [Kiautschou Bay, wasColonialLeaseholdOf, German Empire]
-
A.
colonialProprietorOf
chosen
Indicates that one entity holds colonial proprietorship over another, typically having legal authority to own, govern, or administer a colony or colonial territory.
-
B.
isColonial
Indicates that one entity holds or exhibits colonial status, control, or characteristics in relation to another entity or context.
-
C.
occupiesFormerEstateOf
Indicates that one entity currently resides in, uses, or controls a property that was previously the estate of another entity.
-
D.
formerColonialEntity
Indicates that one entity was previously a colony or colonial possession of another entity.
-
E.
hasColonialName
Indicates that an entity is known by, or has been assigned, a name originating from a colonial power or colonial period.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e02ba6b881908dfafc52d3b75f1c |
completed | May 3, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69f6de09c2f481909f8b2545d3208c9f |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:26 a.m.