Triple
T25712238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reginald de St. Leon |
E644763
|
entity |
| Predicate | receivesSecretOf |
P71015
|
FINISHED |
| Object | inexhaustible wealth |
—
|
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: inexhaustible wealth | Statement: [Reginald de St. Leon, receivesSecretOf, inexhaustible wealth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesSecretOf Context triple: [Reginald de St. Leon, receivesSecretOf, inexhaustible wealth]
-
A.
revealedSecretOf
Indicates that one entity has disclosed or exposed confidential or previously unknown information belonging to another entity.
-
B.
secretes
Indicates that one entity produces and releases a substance from within itself into its surrounding environment or another entity.
-
C.
secretRevealed
Indicates that previously hidden or confidential information has been disclosed to one or more parties.
-
D.
knowsSecret
chosen
Indicates that one entity is aware of confidential or hidden information about another entity or situation.
-
E.
secretRevealedThrough
Indicates that a secret becomes known or disclosed by means of a specified channel, method, or intermediary.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 21, 2026, 9:17 p.m.