Triple
T31437637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carpi |
E801977
|
entity |
| Predicate | romanProvinceInteraction |
P176352
|
FINISHED |
| Object | Dacia |
—
|
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: Dacia | Statement: [Carpi, romanProvinceInteraction, Dacia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanProvinceInteraction Context triple: [Carpi, romanProvinceInteraction, Dacia]
-
A.
romanProvinceRelation
Indicates a relationship where one entity functioned as, or was part of, a Roman province administered by another entity.
-
B.
romanProvinceAfterConquest
Indicates that a territory became a Roman province following its military conquest by Rome.
-
C.
romanProvinceType
Indicates that an entity is classified as a specific type or category of Roman province.
-
D.
romanProvinceFormation
Indicates the establishment or formal organization of a territory as a Roman province under Roman administrative control.
-
E.
RomanProvinceContext
Indicates that the subject entity is situated within, associated with, or understood in the administrative and cultural framework of a Roman province.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 30, 2026, 9:03 p.m.