Triple
T1052387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carthage |
E22727
|
entity |
| Predicate | statusInRomanPeriod |
P22322
|
FINISHED |
| Object | Roman colony |
—
|
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: Roman colony | Statement: [Carthage, statusInRomanPeriod, Roman colony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInRomanPeriod Context triple: [Carthage, statusInRomanPeriod, Roman colony]
-
A.
preRomanStatus
Indicates the status or condition of an entity during the period before Roman rule or Roman cultural dominance.
-
B.
underRomanRule
chosen
Indicates that one entity was politically controlled or governed by the Roman state or its authorities.
-
C.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
D.
usesRomanNumerals
Indicates that something represents numbers or sequences using the Roman numeral system rather than standard Arabic digits.
-
E.
hasRomanName
Indicates that an entity is associated with or known by a name derived from or used in ancient Rome.
- 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8b644088190a1f0f00f97941298 |
completed | March 1, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69a4b7309cc481908ed839b0b8d75dbf |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.