Triple
T6823395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Young Germany |
E156954
|
entity |
| Predicate | movementArea |
P43025
|
FINISHED |
| Object | German literature |
—
|
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: German literature | Statement: [Young Germany, movementArea, German literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementArea Context triple: [Young Germany, movementArea, German literature]
-
A.
movementLocation
Indicates a relationship where an entity moves to, from, or through a specified location.
-
B.
movementDomain
chosen
Indicates the general area, medium, or context within which a movement or motion takes place.
-
C.
movementContext
Indicates the situational or environmental conditions under which a movement or motion event occurs, such as its manner, setting, or constraints.
-
D.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
E.
movementAcross
Indicates movement of an entity from one side or area to another, traversing through or over an intervening space or boundary.
- 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_69c688298a288190af3f285d57f76bbe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d580ca448190aa6d52908ca50e39 |
completed | March 27, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.