Triple
T23986343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bois d'Arc Lake |
E604945
|
entity |
| Predicate | impoundmentDate |
P154140
|
FINISHED |
| Object | 2021 |
—
|
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: 2021 | Statement: [Bois d'Arc Lake, impoundmentDate, 2021]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impoundmentDate Context triple: [Bois d'Arc Lake, impoundmentDate, 2021]
-
A.
impoundmentYear
Indicates the year in which something (typically property, funds, or resources) was officially impounded or taken into custody by an authority.
-
B.
impounds
Indicates the act of seizing and holding property, typically by an authority, so it is kept in custody and temporarily removed from the owner’s control.
-
C.
impoundedBy
Indicates that an authority or agent has seized and taken legal custody of an entity, typically restricting its use or movement.
-
D.
impoundedToForm
Indicates that something (typically water) is collected and held back, usually by a barrier or structure, in order to create or form another entity such as a reservoir, lake, or pond.
-
E.
dateOfArrest
Indicates the specific date on which an entity was formally arrested by an authority.
- 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_69e295463f7c8190b1c19dbd114641b9 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2c1d4508190905a3eb2d98a248b |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:36 p.m.