Triple
T25161702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avezzano |
E626454
|
entity |
| Predicate | formerGeographicalFeature |
P169207
|
FINISHED |
| Object | Lake Fucino (drained) |
—
|
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: Lake Fucino (drained) | Statement: [Avezzano, formerGeographicalFeature, Lake Fucino (drained)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerGeographicalFeature Context triple: [Avezzano, formerGeographicalFeature, Lake Fucino (drained)]
-
A.
refersToGeographicFeature
Indicates that one entity makes reference to, denotes, or is associated with a specific geographic feature such as a landform, body of water, or other physical location.
-
B.
associatedBodyOfWaterFormerName
Indicates that a body of water is linked to another name it was known by in the past.
-
C.
physicalFeature
Indicates that one entity possesses or exhibits a particular physical characteristic or attribute.
-
D.
hydronymOf
Indicates that one term is the name of a body of water associated with another geographic entity (e.g., a river, lake, or sea named after a place or feature).
-
E.
seaBedFeature
Indicates that an entity is a physical feature or formation located on or forming part of the seabed.
- F. None of above. chosen
Provenance (4 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f67d691a948190afa7fb19ae7d4ac5 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67c9ec1708190b26ccf402ed7b106 |
completed | May 2, 2026, 10:37 p.m. |
Created at: April 18, 2026, 6:31 a.m.