Triple
T37899003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Reef |
E945355
|
entity |
| Predicate | activatesDuring |
P176798
|
FINISHED |
| Object | large northwest 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: large northwest swells | Statement: [Second Reef, activatesDuring, large northwest swells]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activatesDuring Context triple: [Second Reef, activatesDuring, large northwest swells]
-
A.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
-
B.
likelyActiveDuring
chosen
Indicates that an entity is expected or inferred to be active or functioning during a specified time period or context.
-
C.
activeAfter
Indicates that one entity becomes active only after another specified event, state, or time has occurred.
-
D.
activationTime
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
-
E.
reactivatedDuring
Indicates that an entity becomes active again within the time span or context defined by another event or condition.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 3, 2026, 4:19 p.m.