Triple
T30456551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Age of Anxiety I |
E774876
|
entity |
| Predicate | hasSubsequentMovement |
P47020
|
FINISHED |
| Object | Age of Anxiety II |
—
|
NE NERFINISHED |
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: Age of Anxiety II | Statement: [Age of Anxiety I, hasSubsequentMovement, Age of Anxiety II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubsequentMovement Context triple: [Age of Anxiety I, hasSubsequentMovement, Age of Anxiety II]
-
A.
hasMovementBefore
Indicates that one movement or motion event occurs earlier in time than another movement or motion event.
-
B.
hasSubsequent
chosen
Indicates that one entity occurs, appears, or is positioned after another in a defined sequence or order.
-
C.
hasMovementLegacy
Indicates that an entity carries forward, preserves, or significantly influences the ongoing impact, traditions, or ideals of a particular movement.
-
D.
hasSubmovement
Indicates that a movement or action is composed of, or contains within it, a smaller constituent movement.
-
E.
haveMovementFor
Indicates that an entity exhibits or is assigned a specific type or pattern of movement in relation to another entity or context.
- 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_69f22494fb60819095d893de0284f886 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: April 29, 2026, 8:10 p.m.