Triple
T27845136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campania Ultra |
E703799
|
entity |
| Predicate | historicalRegionWithin |
P105562
|
FINISHED |
| Object | Campania |
—
|
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: Campania | Statement: [Campania Ultra, historicalRegionWithin, Campania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalRegionWithin Context triple: [Campania Ultra, historicalRegionWithin, Campania]
-
A.
historicalRegionCorrespondsTo
Indicates that a historical region matches or aligns with a specific region, territory, or administrative unit in terms of location, extent, or identity.
-
B.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
C.
historicalRegionPartlyIn
chosen
Indicates that a historical region is located partly, but not entirely, within a specified larger area or territory.
-
D.
historicalRegionCode
Indicates that an entity is associated with a specific code identifying a historical region.
-
E.
historicalFocusRegion
Indicates that an entity’s primary historical attention, study, or activity is centered on a particular geographic region.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: April 27, 2026, 6:06 p.m.