Triple
T14121162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lilo Pelekai |
E339907
|
entity |
| Predicate | guardianIs |
P52530
|
FINISHED |
| Object | older 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: older sister | Statement: [Lilo Pelekai, guardianIs, older sister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardianIs Context triple: [Lilo Pelekai, guardianIs, older sister]
-
A.
guardian
Indicates a protective or custodial relationship in which one entity is responsible for the care, safety, or oversight of another.
-
B.
hasGuardianCharacter
Indicates that one entity serves as a guardian or protective character for another entity.
-
C.
hasGuardianFigureType
chosen
Indicates the type or role of a guardian figure associated with an entity.
-
D.
guardianInstitution
Indicates that an institution serves as a guardian or protective authority responsible for the care, oversight, or safeguarding of another entity.
-
E.
guard
Indicates that one entity protects, watches over, or defends another entity or resource from harm, intrusion, or unauthorized access.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de60942a588190beff0058a92f7051 |
completed | April 14, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.