Triple
T28661999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Augusta Raurica |
E725491
|
entity |
| Predicate | timeOfProsperity |
P5317
|
FINISHED |
| Object | 1st century AD |
—
|
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: 1st century AD | Statement: [Augusta Raurica, timeOfProsperity, 1st century AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfProsperity Context triple: [Augusta Raurica, timeOfProsperity, 1st century AD]
-
A.
historicalPeriodOfProsperity
chosen
Indicates a time span in which a society, region, or entity experienced notable economic growth, stability, and overall flourishing.
-
B.
historicalEraOfSuccess
Indicates that an entity achieved notable success or prominence during a specified historical era.
-
C.
prosperedFrom
Indicates that one entity gained benefit, success, or advantage as a result of another entity, event, or circumstance.
-
D.
prosperityReason
Indicates that one entity is prosperous or thriving specifically because of, or as a result of, another entity or factor.
-
E.
prominentDynasty
Indicates that a dynasty holds significant historical, political, or cultural importance relative to other dynasties.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 28, 2026, 4:58 a.m.