Triple
T7673793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States–China relations |
E173810
|
entity |
| Predicate | experiencedRapprochement |
P75340
|
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: [United States–China relations, experiencedRapprochement, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiencedRapprochement Context triple: [United States–China relations, experiencedRapprochement, 1970s]
-
A.
compromiseBetween
Indicates a relationship in which two or more parties mutually adjust their positions or demands to reach a middle-ground agreement.
-
B.
restoredAllianceWith
Indicates that a previously broken or weakened alliance between two entities has been repaired and reestablished.
-
C.
reunitedIn
Indicates that entities who were previously separated have come together again at a specific time or place.
-
D.
closeRelationship
Indicates a strong, intimate, or emotionally significant bond between two entities, suggesting familiarity, trust, and frequent or meaningful interaction.
-
E.
experiencedProcess
chosen
Indicates that an entity has undergone or participated in a particular process or event.
- 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_69c6995703e0819081de77361b602e78 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4 p.m.