Triple
T34957253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T'Pel |
E1008149
|
entity |
| Predicate | spouseShipAssignment |
P94788
|
FINISHED |
| Object | USS Voyager |
—
|
NE NERFINISHED |
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: USS Voyager | Statement: [T'Pel, spouseShipAssignment, USS Voyager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseShipAssignment Context triple: [T'Pel, spouseShipAssignment, USS Voyager]
-
A.
spouseService
Indicates that one person provides a service or assistance specifically for their spouse within the context of a relationship or arrangement.
-
B.
spouseIn
Indicates that one entity is the spouse (married partner) of another entity within a specified context or grouping.
-
C.
spouseOfMilitaryUnit
chosen
Indicates that one entity is the spouse or marital partner of a member associated with the specified military unit.
-
D.
spouseMember
Indicates that one entity is the spouse (married partner) of another entity.
-
E.
spouseAppointedBy
Indicates that a person’s spouse was selected or assigned to a role or position by the referenced appointing entity.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: May 3, 2026, 4 p.m.