Triple
T13760724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weurt lock |
E330598
|
entity |
| Predicate | navigationCategory |
P110850
|
FINISHED |
| Object | inland waterway lock |
—
|
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: inland waterway lock | Statement: [Weurt lock, navigationCategory, inland waterway lock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationCategory Context triple: [Weurt lock, navigationCategory, inland waterway lock]
-
A.
menuCategory
Indicates the classification relationship that assigns an item to a specific section or category within a menu.
-
B.
category
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
C.
catalogCategory
Indicates that an item or entity is assigned to, or belongs within, a specific catalog category.
-
D.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
E.
routeCategory
Indicates the classification or type assigned to a route within a transportation or path network.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0223ab9081909db05334860405e0 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59db0148190bcaf9646403ca64f |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 10:09 p.m.