Triple
T28215948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyril Wilde |
E711312
|
entity |
| Predicate | livedInRelativeObscurity |
P43114
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cyril Wilde, livedInRelativeObscurity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livedInRelativeObscurity Context triple: [Cyril Wilde, livedInRelativeObscurity, true]
-
A.
livedBefore
Indicates that one entity existed or was alive at an earlier time than another entity.
-
B.
isLessKnownFor
Indicates that one entity is recognized or associated with something to a lesser degree than another entity is.
-
C.
gainedProminenceUnder
Indicates that an entity rose to greater importance, influence, or recognition during the leadership, authority, or period associated with another entity.
-
D.
knownBeforeMainstreamSuccessOf
Indicates that one party was aware of or familiar with another party before the latter achieved widespread or mainstream success.
-
E.
hasLimitedRecognition
chosen
Indicates that the subject is acknowledged or accepted only to a small extent, in restricted contexts, or by a limited audience.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6434d0930819098cb7b8c35b0ae52 |
completed | May 2, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:43 p.m.