Triple
T29371501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aufschwung |
E744865
|
entity |
| Predicate | closingCharacter |
P88852
|
FINISHED |
| Object | brilliant |
—
|
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: brilliant | Statement: [Aufschwung, closingCharacter, brilliant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closingCharacter Context triple: [Aufschwung, closingCharacter, brilliant]
-
A.
closingSectionCharacter
chosen
Indicates that one character functions as the closing or terminating symbol for a particular section or block of content in relation to another element.
-
B.
closingMovementCharacter
Indicates a characteristic or quality of the movement involved in closing something (e.g., how the closing action is performed or behaves).
-
C.
closingSequenceFeature
Indicates a feature or element that appears specifically in the closing sequence of an event, process, or media item.
-
D.
closingPosition
Indicates that an entity terminates, finalizes, or brings to an end the position or state of another entity.
-
E.
openingCharacter
Indicates that one entity is the first character or symbol at the beginning of another entity (such as a string, word, or text).
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669ab36008190bc2e3c5dbdd2050d |
completed | May 2, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 2:27 p.m.