Triple
T934363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eumaeus |
E20161
|
entity |
| Predicate | loyaltyTrait |
P1201
|
FINISHED |
| Object | faithful servant |
—
|
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: faithful servant | Statement: [Eumaeus, loyaltyTrait, faithful servant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyTrait Context triple: [Eumaeus, loyaltyTrait, faithful servant]
-
A.
loyaltyProgramEarnings
Indicates the amount or details of rewards or benefits a participant accrues within a loyalty or rewards program.
-
B.
supportsLoyaltyCards
Indicates that an entity provides functionality to accept, manage, or work with loyalty cards for rewards or benefits.
-
C.
allegiance
chosen
Indicates a relationship where one entity is loyal, committed, or obligated in support or service to another entity.
-
D.
commitment
Indicates a sustained obligation or promise that binds an entity to a course of action, relationship, or goal over time.
-
E.
allianceProgram
Indicates a formal cooperative relationship or partnership established between entities under a shared alliance framework or program.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3bcad2481908b83575b2fb80d14 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b299c4d881908a57ac2711676cd7 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.