Triple
T33331997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Madman of El Dorado |
E853429
|
entity |
| Predicate | refersToPersonLoyalty |
P94124
|
FINISHED |
| Object | Spanish Crown (former) |
—
|
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: Spanish Crown (former) | Statement: [The Madman of El Dorado, refersToPersonLoyalty, Spanish Crown (former)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToPersonLoyalty Context triple: [The Madman of El Dorado, refersToPersonLoyalty, Spanish Crown (former)]
-
A.
loyaltyProgramLinkedTo
Indicates that a loyalty program is associated or connected to a particular entity, such that benefits, points, or rewards can be tracked or applied through that relationship.
-
B.
isLoyalTo
chosen
Indicates that one entity consistently supports, respects, or remains faithful to another entity.
-
C.
loyaltySymbolizedBy
Indicates that an instance of loyalty is represented or expressed by a particular symbol or emblem.
-
D.
hasLoyalties
Indicates that an entity feels allegiance or commitment toward one or more other entities or causes.
-
E.
loyaltyProgramOwner
Indicates that one entity is the owner or managing authority of a particular loyalty program associated with 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: May 1, 2026, 1:34 a.m.