Triple
T9764087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wallacea |
E236738
|
entity |
| Predicate | separatedFromSundaShelfBy |
P90506
|
FINISHED |
| Object | deep ocean trenches |
—
|
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: deep ocean trenches | Statement: [Wallacea, separatedFromSundaShelfBy, deep ocean trenches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separatedFromSundaShelfBy Context triple: [Wallacea, separatedFromSundaShelfBy, deep ocean trenches]
-
A.
separatedFromContinent
Indicates that an entity is geographically detached or isolated from a main continental landmass.
-
B.
separatedByInlandSea
Indicates that two land areas are divided from each other by an inland 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.
separatedFromByLand
Indicates that two entities are divided or kept apart from each other by an intervening landmass.
-
E.
seaSeparatedFrom
Indicates that one geographic region or landmass is separated from another by a sea lying between them.
- 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_69ca84d64f6c8190a4ed4e9f5936eda5 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda09ed54c8190a5879e14184cddf4 |
completed | April 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:25 p.m.