Triple
T35313308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Welchman |
E1019836
|
entity |
| Predicate | bearerFieldOfNotability |
P106126
|
FINISHED |
| Object | cryptanalysis |
—
|
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: cryptanalysis | Statement: [Welchman, bearerFieldOfNotability, cryptanalysis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerFieldOfNotability Context triple: [Welchman, bearerFieldOfNotability, cryptanalysis]
-
A.
notableField
Indicates the field, discipline, or area of activity for which an entity is especially known or distinguished.
-
B.
fieldOfNotableBearer
chosen
Indicates the professional or activity domain in which a notable bearer of a name, title, or identifier is recognized.
-
C.
notableFieldOfRecipients
Indicates that the recipients are notable or recognized specifically in a particular field or area of expertise.
-
D.
bearerNotableEvent
Indicates that a bearer (such as a person or entity) is associated with a specific notable event in which they played a significant role.
-
E.
hasNotableRecognitionFor
Indicates that an entity has received notable recognition, such as awards, honors, or distinctions, specifically for another entity or achievement.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7908ec35881909a42f954fb9fa16e |
completed | May 3, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.