Triple
T16578878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindum Colonia |
E402785
|
entity |
| Predicate | wasLaterDevelopedAs |
P1245
|
FINISHED |
| Object | civilian colonia |
—
|
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: civilian colonia | Statement: [Lindum Colonia, wasLaterDevelopedAs, civilian colonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasLaterDevelopedAs Context triple: [Lindum Colonia, wasLaterDevelopedAs, civilian colonia]
-
A.
wasLaterDevelopedBy
Indicates that something (such as an idea, product, or work) was created or further developed at a later time by a specified agent or entity.
-
B.
developedFrom
chosen
Indicates that one entity originates, evolves, or is derived from another as its source or precursor.
-
C.
wasDevelopedIn
Indicates that an entity (such as a product, technology, or work) came into existence or was created during a specific time period or at a particular place.
-
D.
wasOriginallyDevelopedBy
Indicates that something (such as a concept, product, or system) was first created or developed by a particular agent or entity.
-
E.
formerlyDevelopedBy
Indicates that an entity was developed in the past by another entity, but is no longer developed by that same party.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3595f9be88190b01ba628ecf1103d |
completed | April 18, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.