Triple
T35793857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Majorda Beach |
E1034769
|
entity |
| Predicate | waterCurrent |
P126532
|
FINISHED |
| Object | generally calm |
—
|
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: generally calm | Statement: [Majorda Beach, waterCurrent, generally calm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterCurrent Context triple: [Majorda Beach, waterCurrent, generally calm]
-
A.
waterCurrentPreference
Indicates a preference for a particular strength, speed, or type of water current in an environment.
-
B.
oceanCurrent
Indicates the flow of seawater in a consistent direction driven by factors like wind, temperature, and salinity.
-
C.
waterwayDirection
Indicates the directional flow or orientation of a waterway relative to a reference point or path.
-
D.
surfaceWater
Indicates that one entity consists of or contains surface-level water associated with another entity.
-
E.
currentHydrology
chosen
Indicates the present state or characteristics of water flow, distribution, and related hydrological conditions associated with an entity.
- 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_69f76e1575908190aaa306d843b41c14 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:06 p.m.