Triple
T24607444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Ant system |
E609012
|
entity |
| Predicate | hasLockOrTidalLimit |
P2431
|
FINISHED |
| Object | tidal limit near Honing Lock (disused) |
—
|
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: tidal limit near Honing Lock (disused) | Statement: [River Ant system, hasLockOrTidalLimit, tidal limit near Honing Lock (disused)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLockOrTidalLimit Context triple: [River Ant system, hasLockOrTidalLimit, tidal limit near Honing Lock (disused)]
-
A.
hasCanalLock
Indicates that one entity (typically a canal or waterway) includes or is equipped with a canal lock used to raise and lower boats between stretches of water at different levels.
-
B.
hasTidalConnection
Indicates that one entity is linked to another through the movement, influence, or exchange of tidal waters.
-
C.
tidalLock
Indicates that one astronomical body always shows the same face to another because its rotational period matches its orbital period around that body.
-
D.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
E.
hasLock
chosen
Indicates that one entity possesses or is secured by a lock associated with another entity.
- F. None of above.
Provenance (3 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_69e2c4d060e08190ac9f7c49b1036e20 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:31 a.m.