Triple
T38246970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hummanaya Blowhole |
E1013916
|
entity |
| Predicate | spoutsThrough |
P190205
|
FINISHED |
| Object | coastal rock crevice |
—
|
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: coastal rock crevice | Statement: [Hummanaya Blowhole, spoutsThrough, coastal rock crevice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spoutsThrough Context triple: [Hummanaya Blowhole, spoutsThrough, coastal rock crevice]
-
A.
spouts
chosen
Indicates the action of forcefully ejecting or emitting something, typically in a sudden stream or jet, from one entity toward its surroundings.
-
B.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
-
C.
flowsFrom
Indicates that a substance, medium, or influence moves or originates from one entity or location and proceeds outward to another.
-
D.
flowsUltimatelyInto
Indicates that something (typically a fluid, substance, or process) eventually moves or drains into another thing as its final destination, possibly through intermediate stages or paths.
-
E.
spillType
Indicates the specific category or nature of a spill involved in the relationship or event.
- 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_69f76dd7e89c8190b7866bc85aea521b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.