Triple
T8181766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sister Water |
E191078
|
entity |
| Predicate | kinshipMetaphor |
P81305
|
FINISHED |
| Object | sister |
—
|
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: sister | Statement: [Sister Water, kinshipMetaphor, sister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kinshipMetaphor Context triple: [Sister Water, kinshipMetaphor, sister]
-
A.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
-
B.
portraysRelationship
Indicates that one entity depicts, represents, or illustrates a relationship between other entities.
-
C.
geneticRelation
Indicates that two entities are connected through a hereditary or familial genetic relationship.
-
D.
mythologicalFamily
Indicates a familial relationship between entities within a mythological or legendary context.
-
E.
maritalRelations
Indicates a legally or socially recognized spousal relationship or marriage-based connection between two entities.
- 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_69ca82c4538081909404325aa5639483 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4c2e388190b86854f8b1765e61 |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb45503eec8190aeef0da6c3324710 |
completed | March 31, 2026, 3:53 a.m. |
Created at: March 30, 2026, 5:40 p.m.