Triple
T27925315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Cove, Stanton Drew |
E707816
|
entity |
| Predicate | ceremonialOrRitualSignificance |
P141481
|
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: [The Cove, Stanton Drew, ceremonialOrRitualSignificance, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonialOrRitualSignificance Context triple: [The Cove, Stanton Drew, ceremonialOrRitualSignificance, yes]
-
A.
ritualSignificance
chosen
Indicates that something holds special importance or meaning within a ritual or ceremonial context.
-
B.
ceremonySignificance
Indicates the importance, meaning, or role that a particular ceremony holds within a given context or for specific participants.
-
C.
ceremonialUse
Indicates that something is used in a ritual, religious, or formal ceremony rather than for ordinary or practical purposes.
-
D.
ritualPurpose
Indicates the intended function, goal, or role that a ritual is meant to serve or fulfill.
-
E.
ceremonialSymbol
Indicates that one entity serves as a symbol used in a formal or ritual ceremony for another entity or concept.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 6:59 p.m.