Triple
T3346107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valentia Edetanorum |
E70377
|
entity |
| Predicate | wasRepopulatedInCentury |
P47367
|
FINISHED |
| Object | 1st century BC |
—
|
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 BC | Statement: [Valentia Edetanorum, wasRepopulatedInCentury, 1st century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRepopulatedInCentury Context triple: [Valentia Edetanorum, wasRepopulatedInCentury, 1st century BC]
-
A.
existedInCentury
Indicates that an entity existed or was present during a specified century.
-
B.
rebuiltInCentury
Indicates that an existing structure or entity was reconstructed or significantly rebuilt during a specified century.
-
C.
existsSinceCentury
Indicates that an entity has existed or been in effect since a specified century.
-
D.
reorganizedInCentury
Indicates that an entity underwent a significant reorganization or structural change during the specified century.
-
E.
usedSinceCentury
Indicates that something has been in use starting from a specified century.
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1f4ff888190bf14b9b7fbe9bcee |
completed | March 8, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:12 p.m.