Triple
T17866312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jadzia Dax |
E446713
|
entity |
| Predicate | joinedWithSymbiont |
P18579
|
FINISHED |
| Object | Dax symbiont |
—
|
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: Dax symbiont | Statement: [Jadzia Dax, joinedWithSymbiont, Dax symbiont]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: joinedWithSymbiont Context triple: [Jadzia Dax, joinedWithSymbiont, Dax symbiont]
-
A.
symbiontType
Indicates the specific kind or category of symbiotic relationship that exists between associated organisms.
-
B.
hasCompanionSpecies
Indicates that one entity is accompanied by, or exists in association with, another entity of a different species.
-
C.
wasCompanionOf
Indicates that one entity accompanied or associated closely with another, typically as a partner, ally, or fellow participant over some period of time.
-
D.
containsSymbioticAssociationsWith
chosen
Indicates that one entity includes or encompasses another entity with which it maintains a symbiotic (mutually dependent or beneficial) biological relationship.
-
E.
joinedRebellion
Indicates that an entity became a member or active participant in a rebellion against an established authority.
- 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_69d8b9f4c22c819093c2680434472894 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49793a2588190bb341ac606d767fe |
completed | April 19, 2026, 8:51 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.