Triple
T14567322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Immigrant |
E341816
|
entity |
| Predicate | hasIllRelative |
P7844
|
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: [The Immigrant, hasIllRelative, sister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIllRelative Context triple: [The Immigrant, hasIllRelative, sister]
-
A.
hasFamilialTieTo
chosen
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
B.
hasHouseholdMember
Indicates that one entity is a member of the same household as another entity.
-
C.
hasNotableFamilyMembers
Indicates that an entity is related to one or more family members who are considered notable or significant in some context.
-
D.
closestLivingRelatives
Indicates that the related entities are the most closely related to each other among all currently living entities, in terms of evolutionary or genealogical proximity.
-
E.
hasFamilyFriend
Indicates that one entity has another entity as a friend who is connected through family ties or close familial relationships.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb38d89fc819086709fd3607b835f |
completed | April 14, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69de5c57489c8190b57917be1dba6ae6 |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:23 a.m.