Triple
T11846533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Argus |
E281791
|
entity |
| Predicate | loyaltyReason |
P101827
|
FINISHED |
| Object | served Hera as her watchman |
—
|
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: served Hera as her watchman | Statement: [Argus, loyaltyReason, served Hera as her watchman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyReason Context triple: [Argus, loyaltyReason, served Hera as her watchman]
-
A.
loyaltyDimension
Indicates the degree or aspect of loyalty characterizing the relationship between entities.
-
B.
loyaltyIncentive
Indicates a relationship where benefits or rewards are provided to encourage or recognize continued commitment or repeat engagement.
-
C.
loyaltyQuestionedBy
Indicates that one entity’s loyalty or faithfulness is being doubted, challenged, or called into question by another entity.
-
D.
isLoyalTo
Indicates that one entity consistently supports, respects, or remains faithful to another entity.
-
E.
loyaltySymbolizedBy
Indicates that an instance of loyalty is represented or expressed by a particular symbol or emblem.
- 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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65b5ff08190bb58361f6a6acdca |
completed | April 10, 2026, 7:27 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.