Triple
T32877082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vulcan ceremonial arena |
E840956
|
entity |
| Predicate | ceremoniesConducted |
P129522
|
FINISHED |
| Object | formal bonding rituals |
—
|
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: formal bonding rituals | Statement: [Vulcan ceremonial arena, ceremoniesConducted, formal bonding rituals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremoniesConducted Context triple: [Vulcan ceremonial arena, ceremoniesConducted, formal bonding rituals]
-
A.
ceremonyHeld
Indicates that a formal ceremony or ritual event has taken place at a particular time and/or location.
-
B.
hasCeremonies
chosen
Indicates that an entity conducts, includes, or is associated with one or more formal ceremonies or ritual events.
-
C.
ceremonyKnownAs
Indicates that a particular ceremony is referred to or recognized by a specific name or title.
-
D.
ceremonialConclusion
Indicates the formal ending or closing phase of a ceremony or ritual.
-
E.
ceremonialAction
Indicates an action performed as part of a formal ceremony or ritual, typically following prescribed traditions or symbolic procedures.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:18 a.m.