Triple
T35068747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonia Copia Felix Munatia Lugdunum |
E1011806
|
entity |
| Predicate | wasColonyType |
P30272
|
FINISHED |
| Object | Roman veteran colony |
—
|
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: Roman veteran colony | Statement: [Colonia Copia Felix Munatia Lugdunum, wasColonyType, Roman veteran colony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasColonyType Context triple: [Colonia Copia Felix Munatia Lugdunum, wasColonyType, Roman veteran colony]
-
A.
wasColonyOf
Indicates that one entity functioned as a colony under the political control or administration of another entity.
-
B.
wasColoniaIn
Indicates that a place or settlement functioned as a Roman colonia within a specified larger territorial or administrative unit.
-
C.
colonyType
chosen
Indicates the specific classification or kind of colony associated with an entity (e.g., its organizational or structural type).
-
D.
colonyOf
Indicates that one entity is a colony belonging to, founded by, or politically dependent on another entity.
-
E.
isColonial
Indicates that one entity holds or exhibits colonial status, control, or characteristics in relation to another entity or context.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:01 p.m.