Triple
T10090928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T’Pau |
E215341
|
entity |
| Predicate | roleInEpisode |
P31161
|
FINISHED |
| Object | presides over Spock’s koon-ut-kal-if-fee 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: presides over Spock’s koon-ut-kal-if-fee ceremony | Statement: [T’Pau, roleInEpisode, presides over Spock’s koon-ut-kal-if-fee ceremony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInEpisode Context triple: [T’Pau, roleInEpisode, presides over Spock’s koon-ut-kal-if-fee ceremony]
-
A.
narrativeRoleInSeries
Indicates the specific narrative function or role an entity plays within a particular series or serialized work.
-
B.
roleInSeason
Indicates the specific role or function an entity has within a particular season of a series or competition.
-
C.
roleInScene
chosen
Indicates that an entity participates in a particular scene with a specific role or function within that scene.
-
D.
actorRole
Indicates that an entity participates in an event or action in a specific capacity or function (such as performer, initiator, or responsible party).
-
E.
playsInRole
Indicates that an entity performs or appears in a specific role within a production, event, or context.
- 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd05aa02081908fba02e7085c6d7c |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:01 p.m.