Triple
T7545233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manning River |
E178383
|
entity |
| Predicate | hasIslandInEstuary |
P32399
|
FINISHED |
| Object | Oxley Island |
—
|
NE NERFINISHED |
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: Oxley Island | Statement: [Manning River, hasIslandInEstuary, Oxley Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIslandInEstuary Context triple: [Manning River, hasIslandInEstuary, Oxley Island]
-
A.
hasEstuaryNear
Indicates that the estuary of a water body is located in close proximity to a specified place or feature.
-
B.
hasEstuaryType
Indicates the specific type or classification of an estuary associated with a given water body or location.
-
C.
hasCityOnEstuary
Indicates that a city is located on or adjacent to the estuary of a river.
-
D.
hasIslandAtMouth
chosen
Indicates that a geographic feature, typically a river, has an island located at or near its mouth where it meets a larger body of water.
-
E.
estuaryLocatedIn
Indicates that an estuary is geographically situated within or along the boundaries of a specified larger region or area.
- 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.