Triple
T10825886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benevolent Dictator For Life (historical) |
E255496
|
entity |
| Predicate | impliesTrust |
P9393
|
FINISHED |
| Object | highly trusted leader |
—
|
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: highly trusted leader | Statement: [Benevolent Dictator For Life (historical), impliesTrust, highly trusted leader]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliesTrust Context triple: [Benevolent Dictator For Life (historical), impliesTrust, highly trusted leader]
-
A.
hasTrust
Indicates that one entity has confidence in the reliability, integrity, or good intentions of another entity.
-
B.
confidesIn
Indicates that one entity shares private, sensitive, or personal information or feelings with another entity in trust.
-
C.
implies
Indicates that the truth of one statement guarantees or leads logically to the truth of another statement.
-
D.
typeOfTrust
chosen
Indicates the specific kind or category of trust that characterizes the relationship between entities.
-
E.
trustModel
Indicates that one entity relies on or has confidence in the reliability, integrity, or performance of another entity or system.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d734d0389c819090a892693c4046ed |
completed | April 9, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.