Triple
T31260761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosentia |
E797110
|
entity |
| Predicate | wasConqueredInCentury |
P32947
|
FINISHED |
| Object | 3rd century BC |
—
|
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: 3rd century BC | Statement: [Cosentia, wasConqueredInCentury, 3rd century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasConqueredInCentury Context triple: [Cosentia, wasConqueredInCentury, 3rd century BC]
-
A.
conquestYear
Indicates the year in which one entity successfully conquered or took control over another entity.
-
B.
servedInCentury
Indicates that an entity’s period of service or activity took place during a specified century.
-
C.
collapseCentury
Indicates that one time period or event causes or undergoes a breakdown or compression of its century-level temporal distinction, effectively merging or reducing it into a different or broader timeframe.
-
D.
colonizedInCentury
Indicates that an entity established a colony or began colonizing another place during a specified century.
-
E.
conqueredIn
chosen
Indicates that one entity gained control over another entity or territory as a result of a specific conquest event or campaign.
- 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_69f224dd5fdc81908a4cd24917b67668 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:12 p.m.