Triple
T34237152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yalta Agreement on the Far East |
E878366
|
entity |
| Predicate | disclosedToPublic |
P5035
|
FINISHED |
| Object | post-World War II |
—
|
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: post-World War II | Statement: [Yalta Agreement on the Far East, disclosedToPublic, post-World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disclosedToPublic Context triple: [Yalta Agreement on the Far East, disclosedToPublic, post-World War II]
-
A.
publiclyDisplayed
Indicates that something is shown or made visible in a public context or setting, accessible to people at large.
-
B.
discloses
chosen
Indicates that one entity reveals, makes known, or provides previously non-public information to another entity or to the public.
-
C.
permitsDisclosureTo
Indicates that one party grants authorization for information to be revealed or shared with another specified party.
-
D.
disclosureLevel
Indicates the extent or degree to which information is revealed, shared, or made accessible in a given context.
-
E.
isRevealedTo
Indicates that previously hidden or unknown information becomes known to a specific entity or group.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710de62d48190a1ddc9bee7314a91 |
completed | May 3, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:56 a.m.