Triple
T35017316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Project Paperclip |
E1010087
|
entity |
| Predicate | notablePersonRecruited |
P7128
|
FINISHED |
| Object | Wernher von Braun |
E63695
|
NE 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: Wernher von Braun | Statement: [Project Paperclip, notablePersonRecruited, Wernher von Braun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePersonRecruited Context triple: [Project Paperclip, notablePersonRecruited, Wernher von Braun]
-
A.
notableRecruit
Indicates that an entity is recognized as a significant or high-profile addition to an organization, group, or team.
-
B.
notablePersonDiscussed
Indicates that the subject entity includes or features a discussion about the referenced notable person.
-
C.
notablePublicFigure
Indicates that the subject is widely recognized and holds a significant public profile or influence in society.
-
D.
notablePersonnel
chosen
Indicates that the subject has associated individuals who are particularly important, distinguished, or prominent in relation to it.
-
E.
holderNotableFor
Indicates that a holder (such as a person or organization) is particularly known or recognized for a specific role, achievement, work, or characteristic.
- F. None of above.
Provenance (4 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37bd1d97c0819080f01cf6964bcca5 |
completed | June 21, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.