Triple
T9442820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thurii |
E227687
|
entity |
| Predicate | wasRomanProtectorate |
P88213
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Thurii, wasRomanProtectorate, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRomanProtectorate Context triple: [Thurii, wasRomanProtectorate, true]
-
A.
romanProvinceAfterConquest
Indicates that a territory became a Roman province following its military conquest by Rome.
-
B.
wasRomanTown
Indicates that the subject entity functioned as a town or urban settlement during the period of the Roman Empire.
-
C.
laterRomanAdministrativeUnit
Indicates that one entity functioned as an administrative unit within the later Roman Empire in relation to another entity.
-
D.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
-
E.
RomanTribe
Indicates a relationship where an entity belongs to, is classified within, or is associated with a specific Roman tribe.
- 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.