Triple
T23058806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fucino plain |
E574237
|
entity |
| Predicate | drainageCompletedIn |
P150811
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Fucino plain, drainageCompletedIn, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drainageCompletedIn Context triple: [Fucino plain, drainageCompletedIn, late 19th century]
-
A.
drainageStatus
Indicates the condition or effectiveness of water removal or runoff from an area, surface, or system.
-
B.
drainedDuring
Indicates that one entity had its resources, energy, or contents depleted in the course of another event or process.
-
C.
drainageResult
Indicates the outcome or effect produced by a drainage process or activity.
-
D.
drainedIn
Indicates that a liquid, resource, or substance has flowed out from one entity and been discharged or emptied into another entity or location.
-
E.
drainageAttemptedBy
Indicates that an action to drain fluid or liquid from something was attempted by a specified agent or entity.
- 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_69e245ba7ae48190be606dbc54120e39 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1899e6c788190a2a862122cae8dc3 |
completed | April 29, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:55 p.m.