Triple
T1178509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Germany |
E25081
|
entity |
| Predicate | hadPlannedEconomy |
P252
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [East Germany, hadPlannedEconomy, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPlannedEconomy Context triple: [East Germany, hadPlannedEconomy, true]
-
A.
economicTransition
Indicates a change in an entity’s economic system, structure, or status from one state or model to another.
-
B.
establishedAsSocialistState
Indicates that an entity formally created or declared another entity to be a socialist state as its system of governance.
-
C.
economicPlanningBody
Indicates that an entity functions as an organization responsible for formulating, coordinating, or overseeing economic plans and policies.
-
D.
economicSystem
chosen
Indicates the type or structure of the economic organization or system under which an entity operates or to which it belongs.
-
E.
hasEconomicProgram
Indicates that an entity possesses, implements, or is associated with a specific economic plan, policy framework, or set of economic measures.
- 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_69a494267b4c819088c97a59182bf56a |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd53e4b48190abb2167f8074a6bc |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5844348190b01ac6506906ba3b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.