Triple
T31404499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Val d’Agri |
E801090
|
entity |
| Predicate | hasHistoricalPeriodOfSettlement |
P58089
|
FINISHED |
| Object | Roman era |
—
|
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 era | Statement: [Val d’Agri, hasHistoricalPeriodOfSettlement, Roman era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalPeriodOfSettlement Context triple: [Val d’Agri, hasHistoricalPeriodOfSettlement, Roman era]
-
A.
hasSettlementHistory
Indicates that an entity has a documented history of human settlement or habitation in relation to another entity (such as a place or time period).
-
B.
hasSettlementContinuitySince
Indicates that a settlement has existed continuously at a location since a specified point in time.
-
C.
hasHistoryPeriod
chosen
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
D.
associatedSettlementPeriod
Indicates a temporal period during which a particular settlement is or was occupied, active, or otherwise relevant.
-
E.
settlementPeriod
Indicates the length of time between a transaction or agreement and its final settlement or completion.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: April 29, 2026, 9:20 p.m.