Triple
T30571182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Divorce Beach |
E778124
|
entity |
| Predicate | isOppositeSideOf |
P36358
|
FINISHED |
| Object | Lover's Beach |
—
|
NE NERFINISHED |
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: Lover's Beach | Statement: [Divorce Beach, isOppositeSideOf, Lover's Beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOppositeSideOf Context triple: [Divorce Beach, isOppositeSideOf, Lover's Beach]
-
A.
isBSideOf
Indicates that one entity is located on the B side or secondary face of another entity, typically in a two-sided or dual-orientation context.
-
B.
hasOpposingSide
chosen
Indicates that one entity possesses or is associated with another entity that lies on the opposite or facing side relative to a reference orientation or boundary.
-
C.
hasOppositeDirectionTo
Indicates that one entity’s direction is exactly reversed or opposed to the direction of another entity.
-
D.
isOppositeSideOfValleyFrom
Indicates that two entities are located on facing sides of the same valley, with the valley lying between them.
-
E.
onSide
Indicates that one entity is positioned along or adjacent to the side of another 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68912596881908b658c3082856c7e |
completed | May 2, 2026, 11:30 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:22 p.m.