Triple
T3868809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky Lock |
E91926
|
entity |
| Predicate | hasChamberLength |
P51573
|
FINISHED |
| Object | 600 feet |
—
|
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: 600 feet | Statement: [Kentucky Lock, hasChamberLength, 600 feet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChamberLength Context triple: [Kentucky Lock, hasChamberLength, 600 feet]
-
A.
hasChamber
Indicates that one entity possesses, contains, or is associated with a distinct enclosed space or compartment (a chamber).
-
B.
hasChamberStructure
Indicates that an entity possesses a specific internal chamber or compartmentalized structural organization.
-
C.
hasChamberName
Indicates that an entity is associated with or identified by a specific chamber name.
-
D.
hasChamberAbove
Indicates that one chamber is positioned vertically above another chamber in a spatial or structural arrangement.
-
E.
hasChambersFor
Indicates that one entity contains or provides designated chambers or compartments intended for use by another 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec3dfb3c8190a0a07070f0d76bf6 |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee80858a481909961a33fb50ff8d1 |
completed | March 9, 2026, 3:32 p.m. |
Created at: March 9, 2026, 3:20 p.m.