Triple
T17417766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historic Compromise strategy |
E423528
|
entity |
| Predicate | appliedInDecade |
P4118
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [Historic Compromise strategy, appliedInDecade, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedInDecade Context triple: [Historic Compromise strategy, appliedInDecade, 1970s]
-
A.
usedInDecade
chosen
Indicates that something was in use or commonly utilized during a specified decade.
-
B.
endedInDecade
Indicates that an event, process, or state concluded during a specified decade.
-
C.
proposedInDecade
Indicates that something (such as an idea, theory, law, or proposal) was first formally proposed during a specific decade.
-
D.
adoptedInDecade
Indicates that an entity was adopted or formally taken up during a specific ten-year time period (decade).
-
E.
developmentStartDecade
Indicates the decade during which the development or creation of an entity was initiated.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44233c7888190a4d2aa703b206851 |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.