Triple
T3072206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walter Dornberger |
E64049
|
entity |
| Predicate | laterWork |
P44275
|
FINISHED |
| Object | U.S. aerospace development |
—
|
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: U.S. aerospace development | Statement: [Walter Dornberger, laterWork, U.S. aerospace development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterWork Context triple: [Walter Dornberger, laterWork, U.S. aerospace development]
-
A.
lastWork
Indicates that one entity is the most recent work (e.g., creation, project, or publication) associated with another entity.
-
B.
otherWork
Indicates that one work is related to another work by the same creator, but is distinct from the primary or referenced work.
-
C.
laterActivity
Indicates that one activity occurs after another in time, establishing a temporal ordering between them.
-
D.
workOn
Indicates that an agent is actively engaged in performing tasks or making progress on a particular project, object, or assignment.
-
E.
secondWork
Indicates that one work is the second in order relative to another work within a sequence or set.
- F. None of above. chosen
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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada14c8bd881909cf1bb2649ba36db |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f7630c81908e1ca8a69611cff6 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:02 p.m.