Triple
T38212513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holly Berenson |
E1010587
|
entity |
| Predicate | coGuardianOf |
P190296
|
FINISHED |
| Object | Sophie |
—
|
NE NERFINISHED |
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: Sophie | Statement: [Holly Berenson, coGuardianOf, Sophie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coGuardianOf Context triple: [Holly Berenson, coGuardianOf, Sophie]
-
A.
guardian
Indicates a protective or custodial relationship in which one entity is responsible for the care, safety, or oversight of another.
-
B.
dragonGuardian
Indicates that one entity serves as a protective guardian, specifically in the form or role of a dragon, over another entity.
-
C.
guardianInPlot
Indicates that one entity serves as a guardian or protector of another entity within the context of a specific plot or storyline.
-
D.
starGuardOfChampion
Indicates that one entity serves as the primary or most prominent protector or guardian of a champion.
-
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. 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc42b9334819099929649b7ef68ea |
completed | May 7, 2026, 4:56 p.m. |
Created at: May 3, 2026, 4:30 p.m.