Triple
T4162490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindum Colonia |
E91562
|
entity |
| Predicate | elevatedToStatus |
P3787
|
FINISHED |
| Object | 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: colonia | Statement: [Lindum Colonia, elevatedToStatus, colonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToStatus Context triple: [Lindum Colonia, elevatedToStatus, colonia]
-
A.
elevatedTo
chosen
Indicates that one entity is promoted or raised to a higher rank, status, position, or level relative to another.
-
B.
upgradedStatusTo
Indicates that one entity has changed another entity’s status or level to a higher or more advanced state.
-
C.
strengthenedStatusOf
Indicates that the status, condition, or standing of one entity has been made stronger or more robust in relation to another entity or context.
-
D.
upgradeStatus
Indicates the current state or progress of an upgrade process applied to an entity.
-
E.
elevatedToPrincipalityBy
Indicates that an entity was raised in status or rank to a principality by another entity or authority.
- 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_69aed9626ebc8190a39de631788bea3e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.