Triple
T34953686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zips |
E1008068
|
entity |
| Predicate | wasColonizedIn |
P182459
|
FINISHED |
| Object | 13th century |
—
|
LITERAL 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: 13th century | Statement: [Zips, wasColonizedIn, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasColonizedIn Context triple: [Zips, wasColonizedIn, 13th century]
-
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
Indicates that one entity functioned as a colony under the political control or administration of another entity.
-
C.
regionOfColonization
Indicates the geographic area or territory where a colonizing entity establishes and exercises colonial control.
-
D.
hasColonialEraInteractionWith
Indicates a relationship in which two entities were involved with each other during the colonial era, such as through governance, trade, conflict, or other forms of interaction tied to colonial rule.
-
E.
colonizedInCentury
Indicates that an entity established a colony or began colonizing another place during a specified century.
- F. None of above. chosen
Provenance (4 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78d7211a48190bfb59c406f0bf12f |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c6014e08190864785a4fe3e8e73 |
completed | May 3, 2026, 5:56 p.m. |
Created at: May 3, 2026, 4 p.m.