Triple
T3205801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swami Rock |
E67157
|
entity |
| Predicate | hasAlternativeContext |
P46158
|
FINISHED |
| Object | sometimes called Lovers Leap area |
—
|
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: sometimes called Lovers Leap area | Statement: [Swami Rock, hasAlternativeContext, sometimes called Lovers Leap area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeContext Context triple: [Swami Rock, hasAlternativeContext, sometimes called Lovers Leap area]
-
A.
hasAlternateMemberType
Indicates that an entity is associated with a different or substitute type of member than its primary or standard member type.
-
B.
hasLanguageContext
Indicates that an entity is associated with or interpreted within a specific language or linguistic context.
-
C.
isAlternativeTo
Indicates that one entity can serve as a substitute or different option in place of another.
-
D.
hasAlternativeZoneInCountry
Indicates that an entity has an alternative zone or area located within the specified country.
-
E.
hasTypicalUseContext
Indicates that something is commonly or characteristically used within a particular situation, setting, or context.
- F. None of above. chosen
Provenance (4 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_69ad8589bd988190afa7ed2bdffb7b33 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaa559848819082d1e61f586278dd |
completed | March 8, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada0f9259c8190afbc5ad0fa55436b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:07 p.m.