Triple
T20342459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anytos |
E495772
|
entity |
| Predicate | guardianType |
P52530
|
FINISHED |
| Object | divine attendant |
—
|
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: divine attendant | Statement: [Anytos, guardianType, divine attendant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardianType Context triple: [Anytos, guardianType, divine attendant]
-
A.
guardian
Indicates a protective or custodial relationship in which one entity is responsible for the care, safety, or oversight of another.
-
B.
hasGuardianFigureType
chosen
Indicates the type or role of a guardian figure associated with an entity.
-
C.
bodyguardType
Indicates the specific role or category of bodyguard service associated with an entity.
-
D.
typicalGuard
Indicates that an entity commonly or characteristically serves in a guarding or protective role relative to another entity or context.
-
E.
guardianInstitution
Indicates that an institution serves as a guardian or protective authority responsible for the care, oversight, or safeguarding of another entity.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67836b72081908be65115abdb37bf |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:24 a.m.