Triple
T32876940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T’Pau (Star Trek character) |
E840953
|
entity |
| Predicate | ceremonyOfficiated |
P99224
|
FINISHED |
| Object | Spock and T’Pring’s marriage ceremony |
—
|
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: Spock and T’Pring’s marriage ceremony | Statement: [T’Pau (Star Trek character), ceremonyOfficiated, Spock and T’Pring’s marriage ceremony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceremonyOfficiated Context triple: [T’Pau (Star Trek character), ceremonyOfficiated, Spock and T’Pring’s marriage ceremony]
-
A.
officiatedEvent
chosen
Indicates that an entity formally presided over, supervised, or conducted an event in an official capacity.
-
B.
ceremonyPresidedBy
Indicates that a ceremony is overseen, led, or officially conducted by a particular person or authority.
-
C.
hasPublicCeremony
Indicates that a public ceremony is held or conducted in relation to the subject entity.
-
D.
ceremonyHeld
Indicates that a formal ceremony or ritual event has taken place at a particular time and/or location.
-
E.
ceremonyType
Indicates the specific kind or category of ceremony associated with an event or relationship.
- 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_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:18 a.m.