Triple
T36354222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proposal Rock |
E895294
|
entity |
| Predicate | hasLocalLore |
P170938
|
FINISHED |
| Object | associated with marriage proposals |
—
|
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: associated with marriage proposals | Statement: [Proposal Rock, hasLocalLore, associated with marriage proposals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalLore Context triple: [Proposal Rock, hasLocalLore, associated with marriage proposals]
-
A.
hasLocalCult
Indicates that an entity is associated with a cult or worship practice that is specific to a particular locality or region.
-
B.
reputationInLore
Indicates how an entity is regarded or reputed within a fictional or narrative lore context.
-
C.
hasCultOrLegend
chosen
Indicates that an entity is associated with, or is the subject of, a cult, myth, or legendary tradition.
-
D.
loreLocation
Indicates that something is the place or setting where related background story, history, or world-building information is situated or associated.
-
E.
hasFolkloreStatus
Indicates that something is recognized or classified as having a status or role within folklore or traditional cultural narratives.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff56ef0a5c8190ae729d66a8cf7fc4 |
completed | May 9, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ff539859c481909ec56310da418688 |
completed | May 9, 2026, 3:32 p.m. |
Created at: May 3, 2026, 4:09 p.m.