Triple
T37197961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleventh Labour of Heracles |
E921644
|
entity |
| Predicate | appleGuardianGroup |
P172395
|
FINISHED |
| Object | Hesperides |
—
|
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: Hesperides | Statement: [Eleventh Labour of Heracles, appleGuardianGroup, Hesperides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appleGuardianGroup Context triple: [Eleventh Labour of Heracles, appleGuardianGroup, Hesperides]
-
A.
supportsFamilyGroupManagementInSettings
Indicates that the system allows managing family groups (e.g., creating, editing, or controlling them) within the settings interface.
-
B.
appleOwner
Indicates that one entity possesses or owns an apple.
-
C.
supportsMultipleAppleIDsPerFamily
Indicates that the subject allows or is compatible with having more than one Apple ID associated with a single family group.
-
D.
usesGroup
Indicates that an entity makes use of, operates with, or relies on a particular group as a collective resource, tool, or participant in some activity or process.
-
E.
protectionGroup
chosen
Indicates a relationship in which one entity provides protection, defense, or safeguarding for another entity or group.
- 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_69f76ea313a08190a54404cd1e47da90 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:15 p.m.