Triple
T27266457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitchells Island |
E687916
|
entity |
| Predicate | separatesFromMainlandBy |
P18114
|
FINISHED |
| Object | Manning River channels |
—
|
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: Manning River channels | Statement: [Mitchells Island, separatesFromMainlandBy, Manning River channels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatesFromMainlandBy Context triple: [Mitchells Island, separatesFromMainlandBy, Manning River channels]
-
A.
isSeparatedFromMainlandBy
chosen
Indicates that one land area is divided from the mainland by a specific intervening body or feature, such as water or terrain.
-
B.
seaSeparatedFrom
Indicates that one geographic region or landmass is separated from another by a sea lying between them.
-
C.
separatedByOceanFrom
Indicates that two entities are located on different landmasses with an ocean lying between them as a separating barrier.
-
D.
separatedFromContinent
Indicates that an entity is geographically detached or isolated from a main continental landmass.
-
E.
separatedByInlandSea
Indicates that two land areas are divided from each other by an inland sea lying between them.
- 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_69ef3557abc481908bf3c146f0f3356a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:56 a.m.