Triple
T7545224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manning River |
E178383
|
entity |
| Predicate | isTidalInSection |
P1735
|
FINISHED |
| Object | lower reaches |
—
|
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: lower reaches | Statement: [Manning River, isTidalInSection, lower reaches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTidalInSection Context triple: [Manning River, isTidalInSection, lower reaches]
-
A.
isTidal
chosen
Indicates that something is influenced or driven by tidal forces or tidal movements.
-
B.
navigableInSection
Indicates that something can be successfully moved through, accessed, or traversed within a specified section or segment.
-
C.
isOnSectionOf
Indicates that one entity is located on, or positioned along, a specific segment or subsection of another entity.
-
D.
hasSectionIn
Indicates that one entity contains or includes another entity as a section or subdivision within it.
-
E.
containsTidalFeatures
Indicates that one entity exhibits observable tidal features caused by gravitational interactions 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f898069881909fa8f9c885c4565b |
completed | March 27, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:48 p.m.