Triple
T275778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hell Gate |
E5245
|
entity |
| Predicate | hasCurrentType |
P8870
|
FINISHED |
| Object | tidal rip |
—
|
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: tidal rip | Statement: [Hell Gate, hasCurrentType, tidal rip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrentType Context triple: [Hell Gate, hasCurrentType, tidal rip]
-
A.
hasCurrent
Indicates that an entity presently possesses, exhibits, or is associated with a particular state, attribute, or resource at the current time.
-
B.
hasOperationType
Indicates the specific kind or category of operation associated with an entity or process.
-
C.
hasStageType
Indicates that an entity is associated with, or classified by, a specific type or category of stage within a process, lifecycle, or workflow.
-
D.
hasCriterionType
Indicates that something is associated with or classified by a specific type of criterion used for evaluation or decision-making.
-
E.
hasModelType
Indicates that an entity is associated with or classified under a specific model type.
- 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_69a257e6c8788190987dfe705ca2912a |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25dec53ac8190912f3d79576131fa |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b7480e881909399beccfc7ffb81 |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c2ca46c81908c61696f31e59a98 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:59 a.m.