Triple
T12901856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scorpion |
E308628
|
entity |
| Predicate | marksStatusChangeForCharacter |
P107352
|
FINISHED |
| Object | Seven of Nine joins Voyager crew |
—
|
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: Seven of Nine joins Voyager crew | Statement: [Scorpion, marksStatusChangeForCharacter, Seven of Nine joins Voyager crew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksStatusChangeForCharacter Context triple: [Scorpion, marksStatusChangeForCharacter, Seven of Nine joins Voyager crew]
-
A.
marksDebutOfCharacter
Indicates that an event, work, or appearance represents the first introduction of a particular character.
-
B.
leadCharacterStatus
Indicates the role or condition of an entity when it serves as the primary or central character in a narrative or context.
-
C.
replacesCharacterInRole
Indicates that one character takes over and performs the same role previously held by another character.
-
D.
removedCharacter
Indicates that a character was taken out or deleted from a text, sequence, or collection.
-
E.
characterNameChange
Indicates that an entity’s character has undergone a change from one name to another.
- F. None of above. chosen
Provenance (4 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971820e008190bf8bc7c392c8bcbb |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9713e45a88190acd346f066093550 |
completed | April 10, 2026, 9:53 p.m. |
Created at: April 9, 2026, 5:40 p.m.