Triple
T17260961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iguvium |
E419006
|
entity |
| Predicate | hasRegionSuccessor |
P90999
|
FINISHED |
| Object | modern Umbria region |
—
|
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: modern Umbria region | Statement: [Iguvium, hasRegionSuccessor, modern Umbria region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionSuccessor Context triple: [Iguvium, hasRegionSuccessor, modern Umbria region]
-
A.
successorInRegion
chosen
Indicates that one entity directly follows or replaces another within a specified region or jurisdiction.
-
B.
hasSubdivisionSuccessor
Indicates that one administrative or territorial subdivision directly succeeds another in an ordered sequence or historical progression.
-
C.
hasSuccessorLanguageInRegion
Indicates that one language is followed or replaced by another language within a specific geographic region.
-
D.
hasPosteriorRegion
Indicates that one entity constitutes or occupies the rear or back (posterior) region of another entity.
-
E.
hasDescendantsRegion
Indicates that an entity has descendants or subordinate elements that are located within, originate from, or are associated with a specified 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e70b00c8190b0380be08afae18d |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.