Triple
T24815395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cotter Dam |
E620906
|
entity |
| Predicate | underwentEnlargement |
P2365
|
FINISHED |
| Object | 2010–2013 |
—
|
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: 2010–2013 | Statement: [Cotter Dam, underwentEnlargement, 2010–2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underwentEnlargement Context triple: [Cotter Dam, underwentEnlargement, 2010–2013]
-
A.
enlargementRound
Indicates that one entity is a specific round or stage in a process of enlargement or expansion of another entity.
-
B.
grewToOver
Indicates that something increased in size, amount, or level until it surpassed a specified threshold.
-
C.
expandedDuring
chosen
Indicates that an entity increased in size, scope, or extent over the course of a specified time period or event.
-
D.
sizeIncreasedTo
Indicates that an entity’s size has changed and reached a specified larger value or magnitude.
-
E.
majorExpansionUnder
Indicates that one entity is undergoing or has undergone a significant enlargement, growth, or extension while being under the authority, control, or scope of another entity.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 18, 2026, 5:02 a.m.