Triple
T23573632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regium Julium |
E580185
|
entity |
| Predicate | preRomanCivilization |
P90719
|
FINISHED |
| Object | Ancient Greece |
—
|
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: Ancient Greece | Statement: [Regium Julium, preRomanCivilization, Ancient Greece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preRomanCivilization Context triple: [Regium Julium, preRomanCivilization, Ancient Greece]
-
A.
preRomanPolity
Indicates that an entity functioned as a political or governmental unit that existed before the establishment or dominance of Roman rule in a given region.
-
B.
preRomanLanguage
Indicates that a language existed or was used in a region before the arrival or dominance of Roman rule or the Latin language.
-
C.
preRomanContext
chosen
Indicates that something exists, occurs, or is situated in a historical or cultural context prior to the Roman period.
-
D.
preRomanPopulation
Indicates that the subject represents the population that existed in a place before the arrival or dominance of Roman civilization.
-
E.
preRomanStatus
Indicates the status or condition of an entity during the period before Roman rule or Roman cultural dominance.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd4cde48190b5e4eb162d772319 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:37 p.m.