Triple
T31141139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | upper Biferno valley |
E793784
|
entity |
| Predicate | inhabitedInAntiquityBy |
P3032
|
FINISHED |
| Object | Pentri |
—
|
NE NERFINISHED |
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: Pentri | Statement: [upper Biferno valley, inhabitedInAntiquityBy, Pentri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inhabitedInAntiquityBy Context triple: [upper Biferno valley, inhabitedInAntiquityBy, Pentri]
-
A.
historicallyInhabitedBy
chosen
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
-
B.
inhabitedSince
Indicates that a place has been continuously or initially occupied or lived in by someone or something starting from a specified time.
-
C.
associatedAncientPeoples
Indicates a relationship where certain ancient peoples are historically or culturally linked or connected to a given entity.
-
D.
inhabitedBy
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
-
E.
governedInAntiquityBy
Indicates that one entity exercised political rule or authority over another entity during ancient or classical historical periods.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:05 p.m.