Triple
T30333648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halder War Diary |
E771554
|
entity |
| Predicate | documentsPositionOfAuthor |
P99555
|
FINISHED |
| Object | Chief of the German General Staff |
—
|
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: Chief of the German General Staff | Statement: [Halder War Diary, documentsPositionOfAuthor, Chief of the German General Staff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentsPositionOfAuthor Context triple: [Halder War Diary, documentsPositionOfAuthor, Chief of the German General Staff]
-
A.
positionOfAuthor
chosen
Indicates the spatial or organizational location associated with an author in relation to some reference context.
-
B.
positionInAuthorOeuvre
Indicates the relative placement or order of a work within an author's overall body of work.
-
C.
authorOfWorkAppearingIn
Indicates that one entity is the creator or writer of a work that appears within another work or publication.
-
D.
authorOrder
Indicates the sequence or ranking of authors associated with a work, specifying each author's position in the authorship list.
-
E.
collectionPublicationAuthor
Indicates that an entity is the author responsible for the publication of a particular collection.
- 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 7:53 p.m.