Triple
T30462325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulla Regia |
E775045
|
entity |
| Predicate | wasColoniaUnder |
P160
|
FINISHED |
| Object | Roman 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: Roman Empire | Statement: [Bulla Regia, wasColoniaUnder, Roman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasColoniaUnder Context triple: [Bulla Regia, wasColoniaUnder, Roman Empire]
-
A.
wasColoniaIn
Indicates that a place or settlement functioned as a Roman colonia within a specified larger territorial or administrative unit.
-
B.
representedColony
Indicates that an entity acted as an official representative or delegate for a particular colony in some context or event.
-
C.
wasColonyOf
chosen
Indicates that one entity functioned as a colony under the political control or administration of another entity.
-
D.
isColonialFoundationOf
Indicates that one entity was established as a colony that later developed into or served as the origin of the other entity.
-
E.
wasLaterColonizedBy
Indicates that one entity became a colony of another entity at a later point in time than some referenced event or colonization.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686f0d838819099ca4d828a246d7f |
completed | May 2, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:10 p.m.