Triple
T10948813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludwigsburg branch |
E258669
|
entity |
| Predicate | documentTypeCollected |
P13313
|
FINISHED |
| Object | investigation files |
—
|
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: investigation files | Statement: [Ludwigsburg branch, documentTypeCollected, investigation files]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentTypeCollected Context triple: [Ludwigsburg branch, documentTypeCollected, investigation files]
-
A.
documentTypeUsed
Indicates that a particular type or category of document is employed or applied in a given context or activity.
-
B.
documentTypeIncluded
chosen
Indicates that a particular document type is contained within, or is part of, a specified set or collection of document types.
-
C.
documentTypeProduced
Indicates that one entity produces, generates, or creates a document of a specified type.
-
D.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
E.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770ec7028819084f5ce2035a128e4 |
completed | April 9, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.