Triple
T36954316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athena’s Fortune |
E914149
|
entity |
| Predicate | emissaryLedgerExists |
P187450
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Athena’s Fortune, emissaryLedgerExists, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emissaryLedgerExists Context triple: [Athena’s Fortune, emissaryLedgerExists, Yes]
-
A.
emissaryLedger
chosen
Indicates a relationship where one party maintains or uses a record (ledger) tracking the activities, communications, or obligations of an emissary or representative.
-
B.
emissaryLedgerRewardType
Indicates the type or category of reward granted through an emissary ledger or emissary-related reward system.
-
C.
hasEmissarySystem
Indicates that an entity possesses or is equipped with an emissary system used to represent, communicate, or act on its behalf.
-
D.
hasEndorser
Indicates that one entity supports, approves, or publicly backs another entity, typically lending it credibility or validation.
-
E.
hasLeader
Indicates that one entity serves as the leader or head 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:13 p.m.