Triple
T31325427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio VI Umbria et Ager Gallicus |
E798869
|
entity |
| Predicate | coastalSectionKnownAs |
P85982
|
FINISHED |
| Object | Ager Gallicus |
—
|
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: Ager Gallicus | Statement: [Regio VI Umbria et Ager Gallicus, coastalSectionKnownAs, Ager Gallicus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalSectionKnownAs Context triple: [Regio VI Umbria et Ager Gallicus, coastalSectionKnownAs, Ager Gallicus]
-
A.
coastName
Indicates that an entity is identified by the name of a specific coast or coastal region.
-
B.
hasCoastalSection
chosen
Indicates that a geographic entity includes at least one section of land that directly borders a sea or ocean.
-
C.
areCoastal
Indicates that the entities are located on or adjacent to a coastline or seashore.
-
D.
hasFamousCoastalRegion
Indicates that an entity possesses or is associated with a well-known coastal area or shoreline region.
-
E.
coastType
Indicates the specific kind or classification of a coastline associated with a geographic area.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 9:15 p.m.