Triple
T34957382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miral Paris |
E1008154
|
entity |
| Predicate | parentsRelationship |
P112368
|
FINISHED |
| Object | married couple on USS Voyager |
—
|
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: married couple on USS Voyager | Statement: [Miral Paris, parentsRelationship, married couple on USS Voyager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentsRelationship Context triple: [Miral Paris, parentsRelationship, married couple on USS Voyager]
-
A.
relationshipToParents
Indicates the type or nature of a person's familial relationship to their parents.
-
B.
parentRelationship
Indicates a familial relationship in which one entity is the parent of another entity.
-
C.
parentsStatus
chosen
Indicates the marital or relational status between a person's parents (e.g., married, divorced, separated, single).
-
D.
familyRelationshipStatus
Indicates the type and state of a familial relationship that exists between two entities.
-
E.
parents
Indicates a parental relationship where one entity is the mother or father of another 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_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 3, 2026, 4 p.m.