Triple
T6892350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lock 10 on the Murray River |
E159076
|
entity |
| Predicate | hasLockNumber |
P73976
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Lock 10 on the Murray River, hasLockNumber, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLockNumber Context triple: [Lock 10 on the Murray River, hasLockNumber, 10]
-
A.
hasNumberOfLocks
Indicates the quantity of locks that an entity possesses or is equipped with.
-
B.
hasLock
Indicates that one entity possesses or is secured by a lock associated with another entity.
-
C.
hasPin
Indicates that one entity possesses, includes, or is equipped with a specific pin (such as a connector pin, security PIN, or fastening pin).
-
D.
hasChamberNumber
Indicates that an entity is associated with a specific chamber identified by a particular number.
-
E.
hasShipLock
Indicates that one entity possesses or is equipped with a ship lock used to control water levels for vessel passage.
- 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_69c6883568c8819081db6407e892cccc |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d930ab548190953291d63cbc721b |
completed | March 27, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b53e9881909ec298daa9f1913b |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:24 p.m.