Triple
T9442825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thurii |
E227687
|
entity |
| Predicate | underRomanRuleBecame |
P88214
|
FINISHED |
| Object | Roman 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 colony | Statement: [Thurii, underRomanRuleBecame, Roman colony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underRomanRuleBecame Context triple: [Thurii, underRomanRuleBecame, Roman colony]
-
A.
underRomanRule
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
-
B.
romanRuleEnded
Indicates that a period of Roman political or administrative control over a place or people has come to an end.
-
C.
postRomanSuccessor
Indicates that one entity serves as the political or cultural successor to another entity following the end of Roman rule.
-
D.
viewedRomanRuleAs
Indicates that one entity regarded or interpreted Roman rule in a particular way or from a particular perspective.
-
E.
consideredByRomeAs
Indicates that something or someone is regarded or classified in a particular way by Rome (e.g., Roman authorities, culture, or legal system).
- 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_69ca843884488190ad6cbe0153088234 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f300cc88190a793712706295c53 |
completed | April 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:50 p.m.