Triple
T5360947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainbow Beach |
E103017
|
entity |
| Predicate | patrolledBeach |
P48449
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rainbow Beach, patrolledBeach, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patrolledBeach Context triple: [Rainbow Beach, patrolledBeach, yes]
-
A.
patrolledBy
Indicates that an area, route, or domain is regularly monitored or guarded by a specific agent or group.
-
B.
isPublicBeach
chosen
Indicates that a beach is designated and accessible for use by the general public, typically without exclusive private restrictions.
-
C.
legalStatusOfBeaches
Indicates the legal classification or regulatory status that applies to beaches within a given jurisdiction or context.
-
D.
hasBeach
Indicates that one entity possesses, includes, or is characterized by a beach as part of its features or environment.
-
E.
involvedLandingBeach
Indicates that an entity (such as a military unit, vessel, or operation) participated in or was associated with activities at a specific landing beach.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd86588af081908c846fcde65724da |
completed | March 20, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.