Triple
T16660211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ʻAuʻau Channel |
E404835
|
entity |
| Predicate | relativeShelterFrom |
P124175
|
FINISHED |
| Object | open-ocean swells |
—
|
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: open-ocean swells | Statement: [ʻAuʻau Channel, relativeShelterFrom, open-ocean swells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeShelterFrom Context triple: [ʻAuʻau Channel, relativeShelterFrom, open-ocean swells]
-
A.
tookRefugeWith
Indicates that one entity sought safety, protection, or shelter by going to and staying with another entity.
-
B.
takenAsRefugeBy
Indicates that one entity is used or relied upon by another entity as a place or source of safety, protection, or refuge.
-
C.
seeksRefugeFrom
Indicates that one entity actively looks for safety, protection, or shelter in order to escape or avoid another entity.
-
D.
hasNearbySanctuary
Indicates that one entity has a sanctuary or place of refuge located close to it in space or distance.
-
E.
areaServedAsShelterFor
Indicates that one entity functioned as a shelter or refuge for another entity, providing protection or a safe place.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37bfe0fb081909f2de38df0ed59d7 |
completed | April 18, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:18 a.m.