Triple
T23803072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief of the Army Command of the Reichswehr |
E589624
|
entity |
| Predicate | Wilhelm Heye_termStart |
P153613
|
FINISHED |
| Object | 1926 |
—
|
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: 1926 | Statement: [Chief of the Army Command of the Reichswehr, Wilhelm Heye_termStart, 1926]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Wilhelm Heye_termStart Context triple: [Chief of the Army Command of the Reichswehr, Wilhelm Heye_termStart, 1926]
-
A.
foundedAsMuseumBy
Indicates that an entity was established or created as a museum by a specific person or organization.
-
B.
Cornelius Ennis
Indicates a relationship or association involving the entity or name “Cornelius Ennis,” such as authorship, attribution, or participation in an event or context.
-
C.
honorsPerson
Indicates that one entity formally recognizes, respects, or pays tribute to a specific person.
-
D.
museumFoundedIs
Indicates that a museum was established or founded in a specific year, date, or time period.
-
E.
notableHistoricalEntity
Indicates that an entity holds recognized historical significance or prominence within a historical context.
- 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_69e25d19fecc8190a5cf39bbb18d5d7f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c74f34108190b11961d634559d2b |
completed | April 29, 2026, 8:54 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:54 p.m.