Triple
T14823673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wamberal Beach |
E348516
|
entity |
| Predicate | patrolledDuring |
P3824
|
FINISHED |
| Object | summer season |
—
|
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: summer season | Statement: [Wamberal Beach, patrolledDuring, summer season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patrolledDuring Context triple: [Wamberal Beach, patrolledDuring, summer season]
-
A.
patrolledBy
Indicates that an area, route, or domain is regularly monitored or guarded by a specific agent or group.
-
B.
isPatrolled
Indicates that an entity is regularly monitored or guarded by an agent or system through patrol activities.
-
C.
capturedDuring
Indicates that one event or state occurred within the temporal span of another, typically representing that something was recorded, seized, or documented while a specific situation or activity was taking place.
-
D.
occurredDuring
chosen
Indicates that one event or action took place within the temporal span of another event or time period.
-
E.
operatedDuring
Indicates that an action, process, or system was functioning or in operation throughout a specified time period 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe7a8dc8190bcb5ecfa1cbf1601 |
completed | April 14, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:51 a.m.