Triple
T7187827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Left |
E167613
|
entity |
| Predicate | declinedRelativeTo |
P19208
|
FINISHED |
| Object | New Left after the 1960s |
—
|
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: New Left after the 1960s | Statement: [Old Left, declinedRelativeTo, New Left after the 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declinedRelativeTo Context triple: [Old Left, declinedRelativeTo, New Left after the 1960s]
-
A.
declinedAround
Indicates that something decreased in value, intensity, or quantity in the time period surrounding a specified point or event.
-
B.
declinedDuring
Indicates that one entity’s value, condition, or status decreased over the course of a specified time period or event.
-
C.
endedOrDeclinedAfter
Indicates that one entity’s involvement, status, or offer concluded or was rejected following the occurrence or completion of another specified event or condition.
-
D.
declineAfter
chosen
Indicates that one entity or value decreases or worsens following another specified event, condition, or point in time.
-
E.
reasonForDecline
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e8e2506881909fc4e81b9b79e873 |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:50 p.m.