Triple
T14505356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabine territory |
E340250
|
entity |
| Predicate | preRomanRegion |
P114491
|
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: [Sabine territory, preRomanRegion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preRomanRegion Context triple: [Sabine territory, preRomanRegion, true]
-
A.
preRomanName
Indicates the name by which an entity (such as a place or people) was known before the Roman period or prior to receiving a Roman-era name.
-
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.
provinceInAntiquity
Indicates that an entity functioned as a province or provincial territory during an ancient or classical historical period.
-
D.
preRomanStatus
Indicates the status or condition of an entity during the period before Roman rule or Roman cultural dominance.
-
E.
preRomanCenterOf
Indicates that a place served as the primary political, cultural, or administrative center of a region or community before the establishment of Roman control or influence.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de94e25a2481908b8394e9a19f3b64 |
completed | April 14, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:21 a.m.