Triple
T13949292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eileen Sherwood |
E335474
|
entity |
| Predicate | hasSisterRelationshipType |
P112373
|
FINISHED |
| Object | younger 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: younger sister | Statement: [Eileen Sherwood, hasSisterRelationshipType, younger sister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSisterRelationshipType Context triple: [Eileen Sherwood, hasSisterRelationshipType, younger sister]
-
A.
hasSister
Indicates that one entity is the sister of another entity.
-
B.
hasSisters
Indicates that one entity has one or more female siblings in relation to another entity.
-
C.
hasSisterCityRelationshipType
Indicates a formal sister-city partnership relationship that exists between two municipalities or cities.
-
D.
isEldestSisterOf
Indicates that one person is the oldest female sibling in relation to another person.
-
E.
hasSisterOrganization
Indicates that one organization is related to another as a sister organization, typically sharing a common parent, affiliation, or parallel status within the same overarching structure.
- 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_69d81c6081b88190b53e317c3370c8fe |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e12171c8190b95746bdd4845def |
completed | April 14, 2026, 12:07 p.m. |
| PD | Predicate disambiguation | batch_69de05a3ccf88190b45c742db483fa08 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:17 p.m.