Triple
T33054735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpes Cottiae |
E845816
|
entity |
| Predicate | createdAsProvinceBy |
P97574
|
FINISHED |
| Object | Emperor Nero |
—
|
NE NERFINISHED |
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: Emperor Nero | Statement: [Alpes Cottiae, createdAsProvinceBy, Emperor Nero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdAsProvinceBy Context triple: [Alpes Cottiae, createdAsProvinceBy, Emperor Nero]
-
A.
provinceCreatedBy
chosen
Indicates that a province was established, formed, or officially created through the action, decision, or authority of a specified agent or entity.
-
B.
separateProvinceCreated
Indicates that a new, distinct province has been established, separating it administratively or territorially from an existing province or region.
-
C.
createdAsDistrict
Indicates that an entity was formally established or designated as a district.
-
D.
establishedAsProvinceIn
Indicates that an entity was formally designated or created as a province in a specified year or time period.
-
E.
createdAs
Indicates that one entity was originally made, designed, or brought into existence in the form, role, or identity specified by another entity.
- 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_69f3495333b8819095e9af56855b9061 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: May 1, 2026, 1:25 a.m.