Triple
T33134152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Bevill Lock and Dam |
E847954
|
entity |
| Predicate | lockUse |
P176129
|
FINISHED |
| Object | commercial barge traffic |
—
|
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: commercial barge traffic | Statement: [Tom Bevill Lock and Dam, lockUse, commercial barge traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lockUse Context triple: [Tom Bevill Lock and Dam, lockUse, commercial barge traffic]
-
A.
lockType
Indicates the specific kind or category of locking mechanism or access restriction applied to an entity or resource.
-
B.
lock
Indicates that an entity secures or fastens another entity so that it cannot be opened, accessed, or changed without authorization.
-
C.
lockedMeans
Indicates that one state, condition, or action guarantees or necessitates another, such that when the first is "locked in," the second must follow.
-
D.
lockWidth
Indicates that the width of one entity is constrained to remain fixed or synchronized relative to another entity or a specified value.
-
E.
lockName
Indicates that an entity has or is associated with a specific lock identifier or name used to distinguish it from other locks.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:27 a.m.